Version 1 (modified by bro, 9 years ago) (diff)

--

  1. Current state of Deluge (v1.3)
  2. State of git-master (To be v1.4)

Current state of Deluge (v1.3)

Deluge v1.3 handles hundreds of torrents fairly well. The GTKUI uses a lot of CPU to render the torrent list, so to keep CPU usage at a minimum it is a good idea to run in deamon/client mode and only connect with to the daemon when you need.

When the torrent list reaches 1000 torrents, the CPU usage gets more and more noticable, the more torrents the slower it gets.

Improvements are needed for Deluge to handle thousands of torrents!

State of git-master (To be v1.4)

git-master has been tested and works well with 2-3000 torrents. Currently the biggest problem is that to make libtorrent v0.16.X handle that many active torrents, the settings active_dht_limit, active_tracker_limit, active_lsd_limit must be set. This is currently not implemented in git-master, but applying the patch proposed in #2257 should solve this.

The following patches have already been applied which improves the speed of Deluge with many torrents greatly:

Proposed patches:

Other issues that need investigation:

  • Adding multiple torrents is very slow. This is because when adding many torrents, one call is made to core.add_torrent_file for each torrent.
  • Pausing/resuming multiple torrents is very slow. This is probably because when a torrent changes state, a lot of operations are done (event listeners in GUI presumable), so with hundreds of torrents changing state the result is too much work needing to be done.
  • CPU usage on an idle daemon can still be around 5%. One possible cause for this is because each torrent class creates a LoopingCall? which causes twisted to do a lot of checking when there are a lot of torrents in the session.
  • Add caching to the data-funcs in torrentview.py/listview.py to reduce unecessary computation (Patch development: https://github.com/bendikro/deluge/commits/master-torrentview-data-funcs-cache)