Hi, if it's about a recent Nutch version: there is no such property. (sorry, if it's taken from http://wiki.apache.org/nutch/FetchOptions: this information is really outdated)
With Nutch 1.9 the following properties are available which will cause threads to be started and stopped to come close to the configured bandwidth: <property> <name>fetcher.bandwidth.target</name> <value>-1</value> <description>Target bandwidth in kilobits per sec for each mapper instance. This is used to adjust the number of fetching threads automatically (up to fetcher.maxNum.threads). A value of -1 deactivates the functionality, in which case the number of fetching threads is fixed (see fetcher.threads.fetch).</description> </property> <property> <name>fetcher.maxNum.threads</name> <value>25</value> <description>Max number of fetch threads allowed when using fetcher.bandwidth.target. Defaults to fetcher.threads.fetch if unspecified or set to a value lower than it. </description> </property> <property> <name>fetcher.bandwidth.target.check.everyNSecs</name> <value>30</value> <description>(EXPERT) Value in seconds which determines how frequently we should reassess the optimal number of fetch threads when using fetcher.bandwidth.target. Defaults to 30 and must be at least 1.</description> </property> Best, Sebastian On 11/25/2014 12:09 AM, Dan Kinder wrote: > Hi, I'm having trouble finding documentation about how bandwidth throttling > is actually implemented in Nutch. Is it implemented, and if so how? Or do > most people just use squid proxies, etc.? > > -dan >
