@copper; although I do agree on your last post about mapped memory and such, there is something else that can limit what rtorrent can do in the long run. Some kernels (newer) and some vendors/installers (not pointing fingers), tweak files like sysctl.conf or even .rtorrent.rc to adjust the send/receive buffer, swappiness, ip backlogging and so on. A combination of these lead to diminised "free" RAM allocatable for the rtorrent-process in the long run and one can see an increase in both cached and swapped memory, two values that are relying on less speedy options of writing/reading data than directly within a reasonable free amount of RAM.
I might have used the wrong term here and there in my story so do correct me if necessary.









1Likes
LinkBack URL
About LinkBacks
Reply With Quote


