Your message dated Sat, 18 Dec 2010 00:25:49 +0100
with message-id <20101218002549.7d8c8...@regolo>
and subject line Re: Bug#607394: deluge: Deluge gets very slow with thousands
of torrents
has caused the Debian Bug report #607394,
regarding deluge: Deluge gets very slow with thousands of torrents
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
607394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607394
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Fri, 17 Dec 2010 19:09:48 -0200
Rafael Cunha de Almeida <[email protected]> wrote:
> Package: deluge
> Version: 1.2.3+git20100712.0b609bf-1
> Severity: normal
>
> [...]
>
> 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 :)
Hi Rafael,
thanks for taking the time! Unfortunately, there isn't much we can do.
Upstream worked on this problem and it should be fixed now (or at least
less evident) in version 1.3, but changes aren't going to be backported
because it would be unpractical (this is upstream's thought).
I'm closing the bug report, thanks for your work.
--
Cristian Greco
GPG key ID: 0xCF4D32E4
signature.asc
Description: PGP signature
--- End Message ---
