My experience in torrent clients(in Microsoft realm) comes from bittorrent, azureus and utorrent. Azureus was too heavy like any Java based progr.(and too complete) instead utorrent is too light,like most C++ progs. and almost the same complete (but not open source i think). Deluge is placed in the middle.
Compared primarily to utorrent(i know the deluge development is in its ealiest fase) i focuse to few "actual carateristics"
a) Periodicaly (at times but continously to "oo") deluge transit from a "normal work status" to a "null work status"

For normal work status I mean he dw/up like every p2p client but after say less 1 minute he go to a null status for more than 1 minute and so on, i mean all connections in dw is zeroed=0KB 0 peers ecc., all elements in gui is 0 like a physical disconnection. My first thought was, that's a gt-gui refresh problem but when i take a look in my connection incoming traffic was also null instead outgoing traffic was extremely low (1,5 2 kbps):oops: . I think the problem comes from deeper. Under the same condition(connection,time) utorrent works fine.
b) DHT contacts is only 0- 4.Too low number respect to utorrent (300- 400)
c) Gui responce time is misurable(time elapsed between mouse-clic and gui-response) but that's probably because python Vs C++
d) deluge download the emule blacklist from http://emulepawcio.sourceforge.net/nieu ... filter.dat (because in your faq the links is broken). In general- type is set to Emule IP list(gzip)although ipfilter.dat is not zipped. Till now i haven't blaklisted peers. What' s wrong?
That's was my first impression.I hope to be clear.
Good job keep it high


To be continued ...
PS: for a term of comparison i try download: http://grml.deb.at/grml_2008.11.iso.torrent
My settings was(from top to down):BANDWIDTH:Global(110, 4, 24, 16, 8, 20), v, v, Per torrent(all -1)
QUEUE:8, 3, 5