YaCy-Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000462YaCyWishlist - Wunschlistepublic2014-09-08 11:482014-12-08 00:02
Reportersmokingwheels 
Assigned ToOrbiter 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionfixed 
ETAnone 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000462: Custom crawler PPM for each job.
DescriptionI would like to be able to set the max PPM of a crawl job depending on the site being crawled because Twitter refuses to give information out if you go to fast, currently everything runs a 10 PPM because of this.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0000964)
Orbiter (manager)
2014-12-08 00:02

there is only a global setting on purpose. If a crawl job for a specific domain performs bad for that domain, thats ok because we reflect the speed or speed demand of all domains specifically. If one domain slows down the crawl for all domains, then that is a bug. The demand for speed controls per domain is superfluous in relation to that strategy.

- Issue History
Date Modified Username Field Change
2014-09-08 11:48 smokingwheels New Issue
2014-12-08 00:02 Orbiter Note Added: 0000964
2014-12-08 00:02 Orbiter Status new => closed
2014-12-08 00:02 Orbiter Assigned To => Orbiter
2014-12-08 00:02 Orbiter Resolution open => fixed


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker