This is a fantastic plugin Ratanak, thank you kindly for sharing.

It seems we're talking apples and oranges unfortunately; unless your home ISP connection is > 100Mbit, cache shouldn't be the slightest of issues with modern hard drives. First thing I'd do in your case CoteRL, is try another PHYSICAL drive without going through network, etc. Need to get all the var...

...since I get this for both uploading and downloading. I did not see mention before that this was happening on the upload side as well. I'm going to assume by your statement that this happens regularly with many peers attached on an active torrent that you're seeding, which would take the possibil...

I suspect a dirty cache issue. Try to run a torrent or two that are active on a ramdrive and you'll see the problem goes away. Tells me that IO is getting clobbered.

Thanks for taking the time to reply CAS. While deletion in itself would have obviously broken deluge (had no libtorrent object), it gave me an epiphany I obviously overlooked... Ultimately ended up renaming the existing object to libtorrent.0.14.12.0.so, copied the fresh 0.16.5.0 object to the worki...

With over 900 connections and those settings, you are going to be seeing quite a bit of overhead (not reported in actual torrent stats). If your uplink is that slow, or if you have to limit it to 20kb/s, you need to wax the -1 for connection limits and bring it down to something sane like 2 or 3. Al...

Greetings, Currently running a source installed Deluge 1.3.5 on Debian Squeeze. $ deluge --version deluge: 1.3.5 libtorrent: 0.14.12.0 Since it seems some earlier versions of libtorrent had some 'issues' with thier end-game algo's causing some havok at the tail end of downloads, I figured it maybe a...