Changes between Version 3 and Version 4 of Development/Vast_amount_of_torrents


Ignore:
Timestamp:
11/09/2013 07:00:37 PM (9 years ago)
Author:
bro
Comment:

Added ticket 2379 to proposed patches.

Legend:

Unmodified
Added
Removed
Modified
  • Development/Vast_amount_of_torrents

    v3 v4  
    2727 * [http://dev.deluge-torrent.org/ticket/2257 Allow setting of active_dht_limit, active_tracker_limit and active_lsd_limit. Fix bugs. (#2257)] (Daemon) 
    2828 * [http://dev.deluge-torrent.org/ticket/2332 Speed optimizations to torrent.get_status (#2257)] (Daemon) 
     29 * [http://dev.deluge-torrent.org/ticket/2379 Move cleanup of prev_status from torrent.py to torrentmanager.py (#2379)] (Daemon) 
    2930 
    3031Other issues that need investigation: 
    3132 * 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. 
    3233 * 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. 
    33  * Each Torrent instance (torrent.py) has a LoopingCall to clean up prev status. With thousands of torrents, this causes constant high CPU usage. [https://github.com/bendikro/deluge/commits/develop-loopingcall This patch moves the LoopingCalls from from Torrent to torrentmanager].  
    3434 * CPU usage on an idle daemon can still be around 5% ([http://dev.deluge-torrent.org/ticket/1490 #1490]). 
    3535 * 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])