Hello.

One of my main problems with ktorrent is its extreme slowness in the UI. I have a 60mbit connection and can upload and download with 8.5MB/s both.

when i do this, ktorrent basically explodes, it becomes mostly useless when this happens, user interface updates happens every 5-10 seconds, making it mostly impossible to do anything.

even worse is when adding big torrents, since i often use network filesystems not supporting the fallocate() stuff for preallocation, thus taking up several minutes of no UI updates.

I dont know why this happens, or how to fix it, i suspect that the UI is already separated from network as one would normally do, but maybe it somehow locks for the aquisition of data to be shown or something? no idea, i havent looekd at the code.

edit: happens on all versions

Also, for my wishes of features. I wish i could setup seed limits on specific groups, like TV group seed 1:1, linux torrents seed indefinitely

Try upping the GUI update interval to 3 seconds. Configure >> Advanced >> GUI update interval (3000 ms).
[Edit: Not that KT really respects this setting very well, my GUI seems to update consistently at something like half the value used. And it caps at 5 secs, for some odd reason.]

If you're speed limiting, play with your Network sleep interval as well. Although with that big a pipe, you can probably disable up/down limits entirely, which will have KT use less CPU.

The disk pre-allocate for big files (several minutes of no UI updates) has always been a problem, as a work around, I just keep KT minimized to the system panel and use the Scan Folder plugin method for adding torrents. This doesn't make KT any faster allocating files, but it does let you keep adding torrent files to the scan directory, so you're not waiting on KT between each one.

For your wish, you can probably get done what you want by hacking my statusChanged.py script (Latest copy: viewtopic.php?f=1&t=4177 ) It changes Max Share Ratios and automatically deletes torrents based upon Share Ratio and/or Seed Time. But note, the API doesn't support doing this with groups, so for now you'll need to use the directory the torrents are in to make the seeding {etc.} decision on.

envious of your pipe,
Sam