nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Nioche (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-207) Bandwidth target for fetcher rather than a thread count
Date Fri, 16 May 2014 10:54:28 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999102#comment-13999102
] 

Julien Nioche commented on NUTCH-207:
-------------------------------------

Hi Sebastian,

Not really. I will revert it back to info when I get to the office tomorrow morning. Thanks!

> 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)

Mime
View raw message