DSM-G600, DNS-3xx and NSA-220 Hack Forum

I don't know if that's the way to go.

Set the (approximate) maximum number of allowed threads (0-999).

Sometimes under certain circumstances the program may create way to many download threads. Most of them are in wait-state. That is not bad, but threads are usually a limited resource. If a program creates to many of them, operating system may kill it. The option <ThreadLimit> prevents that.

NOTE: the number of threads is not the same as the number of connections opened to NNTP-servers. Do not use the option <ThreadLimit> to limit the number of connections. Use the appropriate options <ServerX.Connections> instead.

NOTE: the actual number of created threads can be slightly larger as defined by the option. Important threads may be created even if the number of threads is exceeded. The option prevents only the creation of additional download threads.

NOTE: in most cases you should leave the default value "100" unchanged.
However you may increase that value if you need more than 90 connections (that's very unlikely) or decrease the value if the OS does not allow so many threads. But the most OSes should not have problems with 100 threads.

It's 100 on my ch3snas and it works well.
But my payserver abbo is limited to 2,5 Mbit/s (Which I can max out on my nas.)

(average download rate: 320 KB/s shown by nzbgetweb interface which is exactly where I pay for.)

Don't forget nzbgetweb gives you KiloBytes / second so do the math.

Last edited by perssinaasappel (2009-05-17 22:28:12)