Changes between Version 2 and Version 3 of Development/Vast_amount_of_torrents


Ignore:
Timestamp:
10/06/2013 08:42:52 PM (9 years ago)
Author:
bro
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Development/Vast_amount_of_torrents

    v2 v3  
    3131 * 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. 
    3232 * 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  * CPU usage on an idle daemon can still be around 5% ([http://dev.deluge-torrent.org/ticket/1490 #1490]). 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. 
     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].  
     34 * CPU usage on an idle daemon can still be around 5% ([http://dev.deluge-torrent.org/ticket/1490 #1490]). 
    3435 * 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]) 
    3536 * Reducing the number of calls (executions) torrent.update_state during startup (loading torrents)