Custom Query (2449 matches)
Results (526 - 528 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #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 |
|||
| #3093 | WontFix | Speed regulation ignored. | ||
| Description |
When download speed limit is set to be more than about 4100KB/s, it gets completely ignored and speed is maxed out. Even after setting it back to 4100, it's ignored until deluge is restarted. Client: 1.3.15 libtorrent: 1.1.4.0 Linux 4.11.9-1-ARCH #1 SMP PREEMPT x86_64 |
|||
| #2332 | WontFix | Speed optimizations to torrent.get_status | ||
| Description |
Optimized torrent.get_status by keeping track of if the torrent status has been updated since last call. If not, use the the previous values instead of calling the status functions. I've tested loading deluged with 1000 torrents and connecting thin client and leaving it running for 2 minutes. The number of calls to get_status is around 250000 Current get_status used a total of 15 seconds CPU, while this version used 6 seconds. According to cProfile the average runtime is reduced from 60 to 20 microseconds. The downside is that the code is a bit more verbose. https://github.com/bendikro/deluge/commits/develop-torrent-get-status-speedup |
|||
