Still no answer to this problem of performance ... Or even recognition that there may be a problem!

I admit that I am quite disappointed.

Deluge was one of the best bittorrent software. It is (almost) become worse. I hope it will not last.

danii wrote:I guess it's a bit too much, I had 120 TIME_WAIT at one time, one of the developers will have to say if this is intentional or if this is a bug.

Status TIME_WAIT for connections with peers is normal at most. But not for local sockets between daemon and ui...

As Deluge now runs as a daemon and a separate ui(web, gtk and console) these connections are the ui and daemon communicating with each other, even if you're using Classic mode, under the hood there is still a daemon and a ui running. One (or two or three) socket(s) with status ESTABLISHED to commun...

There must be something wrong with this new version.The same torrent in the old version,it can reach 100k,but it never get 30k in the new version.I hope the next rc can give us some good news. Deluge 1.0.0 is out... but always slower than version 0.5.x. For my experience, the same torrent in versio...

While using deluge 1.0.0, i see many local connections (ubuntu 8.04) : % netstat --inet -n -a | grep 58846 tcp 0 0 127.0.0.1:58846 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:58846 127.0.0.1:39449 TIME_WAIT tcp 0 0 127.0.0.1:58846 127.0.0.1:39450 TIME_WAIT [...] tcp 0 0 127.0.0.1:58846 127.0.0.1:39521 TIME_W...