[
https://issues.apache.org/jira/browse/NUTCH-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Nioche updated NUTCH-207:
--------------------------------
Attachment: NUTCH-207.trunk.v2.patch
Thanks for your comments Seb. Attached is a new version of the patch which
follows most of your suggestions.
* fetcher.bandwidth.target.check.everyNSecs has to be >= 1
* fetcher.maxNum.threads gets default value of numThreads and if specified by
user we check that the value is >= to it.
* simplified the logic for checking whether the functionality is used : we now
need to check only for fetcher.bandwidth.target
* fetcher.bandwidth.target is expressed in kbps, logs use kbps too
* take fetcher.threads.per.host into account
I will document the new parameters in nutch-default when committing.
> 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)
