#2481: multi-threaded torrent checking
-----------------------------+------------------------------------
Reporter: therulerofchina | Owner:
Type: feature-request | Status: new
Priority: minor | Milestone: performance
Component: other/unknown | Version: other (please specify)
Keywords: |
-----------------------------+------------------------------------
from what I can see (please do correct me if I'm wrong and close the
ticket), deluge doesn't seem to like using more than one thread to check a
torrent even when there are several hundred torrents in the queue. This
seems like a waste of resources and time, given that if:the load was
spread across more cores, or n torrents could be checked concurrently
(where n is the number of threads your CPU supports), or there was a
setting to allow you to choose some way to more efficiently use the
resources available, Deluge would be several times faster at starting up
or adding multiple torrents where the data already exists.
tl;dr: spread checking torrents across available cores
sorry if this is a little incoherent, I've had a lot of coffee and not
much sleep
more info on my current system just in case it helps:
#deluged --version
deluged: 1.3.3
libtorrent: 0.15.10.0
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2481>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
