Hey guys,
So 5 of us decided to get a dedicated server.
Following the guide here : http://forums.rutorrent.org/index.php?topic=608.0
I was able to run rtorrent with rutorrent perfectly. Now, i noticed that there is no queuing system in rtorrent. How prefix should i add to .rtorrent.rc to ensure that the lack of this feature wouldn't be abused? I'm afraid that 1 person might just dump 200 torrent files and might take a toll on the server's performance (mainly RAM and CPU usage. Perhaps Disk I/O as well).
I know of the prefix:
scheduler.max_active.set =
However, it is buggy. Lets say i set the value to 2. If i were to add 5 torrents, 2 would be downloading and 3 would be in a paused state. Once those 2 torrents have completed downloading, all 3 torrents would start running. The same if i were to add 8 torrents, and 2 would be downloading. When 1 of the 2 torrents are completed, all 6 torrents would change from paused to downloading.
It can also be reproduced by stopping 1 active torrent, and the other torrents which are in queue would then start downloading. This makes the prefix scheduler.max_active.set = pointless in my opinion.
So what options should i set, to ensure that the lack of the queuing system to not be abused?
So 5 of us decided to get a dedicated server.
Following the guide here : http://forums.rutorrent.org/index.php?topic=608.0
I was able to run rtorrent with rutorrent perfectly. Now, i noticed that there is no queuing system in rtorrent. How prefix should i add to .rtorrent.rc to ensure that the lack of this feature wouldn't be abused? I'm afraid that 1 person might just dump 200 torrent files and might take a toll on the server's performance (mainly RAM and CPU usage. Perhaps Disk I/O as well).
I know of the prefix:
scheduler.max_active.set =
However, it is buggy. Lets say i set the value to 2. If i were to add 5 torrents, 2 would be downloading and 3 would be in a paused state. Once those 2 torrents have completed downloading, all 3 torrents would start running. The same if i were to add 8 torrents, and 2 would be downloading. When 1 of the 2 torrents are completed, all 6 torrents would change from paused to downloading.
It can also be reproduced by stopping 1 active torrent, and the other torrents which are in queue would then start downloading. This makes the prefix scheduler.max_active.set = pointless in my opinion.
So what options should i set, to ensure that the lack of the queuing system to not be abused?