Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve hogging problem #29

Open
don-han opened this issue Mar 11, 2016 · 2 comments
Open

Solve hogging problem #29

don-han opened this issue Mar 11, 2016 · 2 comments

Comments

@don-han
Copy link
Member

don-han commented Mar 11, 2016

No description provided.

@don-han
Copy link
Member Author

don-han commented Mar 11, 2016

@alvinwan
Copy link
Collaborator

Just for future reference, we could use the priority kwarg to take advantage of the inherent PQ that scrapy has built-in for requests. Here was what I posted Slack:

[2:17]
...since higher priority values correspond to, well, higher priority, just
 take the difference between max_depth and the depth of the current
 page and pass that in as the priority. We take the difference because
 we want higher priority to correspond to lower depth, effecting a bfs
 by page-depth. I don't remember if this is the case, but we'd have to
 enqueue all domains first though, so that it doesn't start bfs... on one
 domain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants