Custom Query (2449 matches)
Results (625 - 627 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2250 | Fixed | Speedup removing multiple torrents from core | ||
| Description |
Each call to core.remove_torrent took about 1 second on my machine. Most of time 90%+ was used by writing the state file. When removing multiple torrents, the state file is now written after removing all the torrents. https://github.com/bendikro/deluge/commit/master-core-remove-torrents |
|||
| #2406 | Fixed | Speed up adding multiple torrents | ||
| Description |
Adding large amounts of torrents is painfully slow because the torrents.state and torrents.fastresume files are written to disk after each torrent is added. This patch adds a new function to core which takes multiple torrents so that the state and fastresume files are only written to disk once. GTKUI add dialog uses this function. https://github.com/bendikro/deluge/tree/develop-add-torrents |
|||
| #2696 | Fixed | incorrect destination folder shown in GTK UI | ||
| Description |
I have the global destination folder set to '/u/finished' in preferences-downloads-move completed to. If for a single downloading torrent I change move completed to: on the options tab of the bottom UI panel to something else e.g. /var/torrents/fin UI starts showing 'fin' in the bottom panel for all torrents - even seeding, as on the attached screenshot. It is a cosmetic bug - torrents that have no destination folder explicitely set will be moved to the default destination folder regardless of what is shown in the UI. 1.3.10, kubuntu 14.04, don't remember having this bug in 1.3.7 and I skipped .8 and .9, also I've upgraded ubuntu from 12.04 to 14.04 about the same time as deluge. Also it would've been better if deluge showed full save path here, not the last folder im the path. |
|||
