Rtorrent: Is rtorrent multicore?

Created on 4 May 2020  路  8Comments  路  Source: rakshasa/rtorrent

Hello,

It's more a question than a bug.
I have weak dual core CPU(439 passmarks per core) and fast internet(up to 1GBit/s). Transmission currently can write up to 150-200 MBit/s utilising one core.
Could it be better with rtorrent? Can it use both cores?

Most helpful comment

It's more an issue of IO bandwidth, however certain things are threaded like hash checking.

Actually it is not. Remember the performance metrics we have sent to you half a year ago?
Even a 24 drive server or NVMe array will not run any faster than certain speed on single instance. Only CPU clockspeed seems to matter due to the polling & locking methodology in rtorrent and therefore being limited to single thread managing it all underneath. After that only thing that can boost performance is multiple instances.

We did throw at it an 32core CPU with 256gb ram, 24x drives for just single instance. Only CPU clock speed seemed to matter beyond certain point. It becomes a function of how many connections, torrents etc. are and averages to the swarm speed essentially, if swarm could accept faster, make less connections etc. to ensure rtorrent is not bottlenecking.

Did you ignore all those reports or even read them?

All 8 comments

  • docker > 2 containers with different settings > manual multicore

@DrMythnick possible, thanks.

useless question, please close

I don't think, it is useless question. It would be nice, if there was something like -j N option.

rTorrent is very very lightly multithreaded, in essence your bottleneck is still single core and clock frequency matters above anything else.

Best way to get highest speeds are multiple instances.

It's more an issue of IO bandwidth, however certain things are threaded like hash checking.

It's more an issue of IO bandwidth, however certain things are threaded like hash checking.

Actually it is not. Remember the performance metrics we have sent to you half a year ago?
Even a 24 drive server or NVMe array will not run any faster than certain speed on single instance. Only CPU clockspeed seems to matter due to the polling & locking methodology in rtorrent and therefore being limited to single thread managing it all underneath. After that only thing that can boost performance is multiple instances.

We did throw at it an 32core CPU with 256gb ram, 24x drives for just single instance. Only CPU clock speed seemed to matter beyond certain point. It becomes a function of how many connections, torrents etc. are and averages to the swarm speed essentially, if swarm could accept faster, make less connections etc. to ensure rtorrent is not bottlenecking.

Did you ignore all those reports or even read them?

My first response was reactionary and worse than the uselessness I claimed the the OP was, so apologies for that. Is there any way you can post the metrics in question? Despite my rudeness, I don't think rakshasa has ignored very many legit bug reports.

Was this page helpful?
0 / 5 - 0 ratings