Package: deluge Version: 1.2.3+git20100712.0b609bf-1 Severity: normal I've had to add thousands of torrent files on deluge (2093, so far). Perhaps I'm an unique case, but I didn't expect it to get so slow after only a couple thousand torrents. It takes 100% of cpu during startup during a considerable period of time and throughout the whole operation it doesn't work well. I think it may have something to do with file checks, maybe there should be options to reduce the number of checks or something like that.
Even after everything gets downloaded it's still very slow. Selecting torrents and then clicking in remove torrent is also very slow. So I think the way torrents are stored in memory is probably not very efficient as well. I think if there was a "finished state" where I could go there and delete them all, instead of waiting the torrents showing up in seeding a few at a time, it would be already a good improvement. Because, although slow, I'm able to add all those torrents and I'd be able to delete tem without much human interaction. I know it's a hard thing to track down and fix, perhaps it's not even the intention of the program to work with that many torrents. Anyhow, I thought it wouldn't hurt to report it :) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages deluge depends on: ii deluge-gtk 1.2.3+git20100712.0b609bf-1 bittorrent client written in Pytho ii python 2.6.6-3+squeeze2 interactive high-level object-orie deluge recommends no packages. deluge suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
