

Speedup removing multiple torrents from core (#2250) (GTKUI).Add caching to the data-funcs in ui/gtkui/torrentview_data_funcs.py git commit.Speed optimizations to sessionproxy (#2285) git commit.Cache tracker icons in gtkui (#2248) ( git commit).The following patches have already been applied which improves the speed of Deluge with many torrents greatly: This can also be fixed by using the ltConfig plugin found in the list of plugins.
HOW TO SPEED UP DELUGE TORRENT PROGRAM PATCH
This is currently not implemented in git-develop, but applying the patch proposed in #2257 should solve this. 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. Git-develop has been tested and works well with 2-3000 torrents. Speed optimizations to the torrentview in GTKUI (#2184), git commit.Small (but significant) speed optimizations to the torrentview (#2259) git commit (GTKUI) (smaller version of #2184 for 1.3 branch).Cache tracker icons in gtkui (#2248) git commit (GTKUI).The following patches have been applied to 1.3: When the torrent list reaches 1000 torrents, the CPU usage gets more and more noticable, the more torrents the slower it gets. 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. Tickets for performance issues that have not yet been fixed or applied to the develop branch are listed in the performance milestone.ĭeluge v1.3 handles hundreds of torrents fairly well.
HOW TO SPEED UP DELUGE TORRENT PROGRAM CODE
Deluge 1.3 will not be getting any more optimizations or improvements, so any new code will go into the develop branch.


Most issues with speed gets noticable when the number of torrents grow past a given threshold. We have been working on optimizing Deluge to use less resources and handle more torrents.
