[
https://issues.apache.org/jira/browse/NUTCH-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000980#comment-14000980
]
Hudson commented on NUTCH-207:
------------------------------
SUCCESS: Integrated in Nutch-trunk #2630 (See
[https://builds.apache.org/job/Nutch-trunk/2630/])
NUTCH-207 : reverted fetch log level to info as was prior to patch (jnioche:
http://svn.apache.org/viewvc/nutch/trunk/?view=rev&rev=1595135)
* /nutch/trunk/src/java/org/apache/nutch/fetcher/Fetcher.java
NUTCH-207 Bandwidth target for fetcher rather than a thread count (jnioche:
http://svn.apache.org/viewvc/nutch/trunk/?view=rev&rev=1593694)
* /nutch/trunk/CHANGES.txt
* /nutch/trunk/conf/nutch-default.xml
* /nutch/trunk/src/java/org/apache/nutch/fetcher/Fetcher.java
> Bandwidth target for fetcher rather than a thread count
> -------------------------------------------------------
>
> Key: NUTCH-207
> URL: https://issues.apache.org/jira/browse/NUTCH-207
> Project: Nutch
> Issue Type: New Feature
> Components: fetcher
> Affects Versions: 0.8
> Reporter: Rod Taylor
> Assignee: Julien Nioche
> Fix For: 1.9
>
> Attachments: NUTCH-207.trunk.patch, NUTCH-207.trunk.v2.patch,
> ratelimit.patch
>
>
> Increases or decreases the number of threads from the starting value
> (fetcher.threads.fetch) up to a maximum (fetcher.threads.maximum) to achieve
> a target bandwidth (fetcher.threads.bandwidth).
> It seems to be able to keep within 10% of the target bandwidth even when
> large numbers of errors are found or when a number of large pages is run
> across.
> To achieve more accurate tracking Nutch should keep track of protocol
> overhead as well as the volume of pages downloaded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
