Changes between Version 1 and Version 2 of Development/Vast_amount_of_torrents
- Timestamp:
- 05/25/2013 12:49:56 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Development/Vast_amount_of_torrents
v1 v2 20 20 * [http://dev.deluge-torrent.org/ticket/2248 Cache tracker icons in gtkui (#2248)] ([http://git.deluge-torrent.org/deluge/commit/?id=463ac0c07eda1b33b145e1b9be7edbc0981815a99 master]) ([http://git.deluge-torrent.org/deluge/commit/?h=1.3-stable&id=36a78d8f219f 1.3-stable)] (GTKUI) 21 21 * [http://dev.deluge-torrent.org/ticket/2259 Small (but significant) speed optimizations to the torrentview in GTKUI (#2259)], [http://git.deluge-torrent.org/deluge/commit/?h=1.3-stable&id=a0ae3ebfce826980d08f6e75ec62a48e39cd5b41 1.3-stable] (GTKUI, smaller version of #2184 for 1.3 branch) 22 * [http://dev.deluge-torrent.org/ticket/2285 Speed optimizations to sessionproxy (#2285)] (GTKUI) 22 23 * [http://dev.deluge-torrent.org/ticket/2116 Application layer protocol for transfering RPC messages + utf8 decoding error (#2116)], [http://git.deluge-torrent.org/deluge/commit/?id=8e7432e71c80a47c96bf48c07535ec1991efe1d9 master] (RPC communication between daemon and clients) 23 24 24 25 Proposed patches: 25 * [http://dev.deluge-torrent.org/ticket/2285 Speed optimizations to sessionproxy (#2285)] (GTKUI)26 26 * [http://dev.deluge-torrent.org/ticket/2250 Speedup removing multiple torrents from core (#2250)] (GTKUI) 27 * [http://dev.deluge-torrent.org/ticket/2257 Allow setting of active_dht_limit, active_tracker_limit and active_lsd_limit. Fix bugs. (#2257)] (Daemon) 27 * [http://dev.deluge-torrent.org/ticket/2257 Allow setting of active_dht_limit, active_tracker_limit and active_lsd_limit. Fix bugs. (#2257)] (Daemon) 28 * [http://dev.deluge-torrent.org/ticket/2332 Speed optimizations to torrent.get_status (#2257)] (Daemon) 28 29 29 30 Other issues that need investigation: 30 31 * 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. 31 32 * 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. 32 * 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.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 34 * 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]) 35 * Reducing the number of calls (executions) torrent.update_state during startup (loading torrents)