#2414 closed bug (Fixed)
Connection and the info command are very slow
| Reported by: | ptspts | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | 2.x |
| Component: | GTK UI | Version: | 1.3.6 |
| Keywords: | Cc: |
Description
I have 1500 active torrents in deluged. When I use deluge-console, it connects quickly, but the info command is very slow (it takes more than a minute with 100% CPU usage in the deluge-console process; deluged uses less than 20% CPU).
The same thing happens when establishing the connection from the GTK-UI to deluged: after clicking the *Connect* button, it takes more than a minute to see the torrents with 100% CPU usage in the deluge-console process, and deluged uses less than 20% CPU. Once connected, everything is fast.
How can I diagnose this myself? How should I start the GTK-UI so that I get some CPU profiling info?
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Milestone: | performance → 1.4.0 |
|---|---|
| Resolution: | → Fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
There is little you can do about this. The 1.3.X versions do not handle that many torrents very well. I'm impressed you manage to use it with 1500 torrents. The develop git-branch (to be v1.4) contains speed improvements and handles at least a few thousand torrents fairly well. Also more improvements will hopefully be ready before 1.4 is released, and we expect it to handle tens of thousands of torrents.
See Vast amount of torrents for more info.