1.2_rc2 is definitely a lot better even over 1.2_rc1. I was having enormous speed issues (10-20MB would download per day) until 1.2_rc2 and now the torrents download at 20kB/s or so constantly.

Problem is, I've set the download speed to 10kB/s, and it's going over the limit.

This would normally not be a problem, but the reason I've set it low is that I still have Azureus working on older torrents while I gradually phase it out. With Azureus eating 20-30kB/s itself and KTorrent eating around 20kB/s, most of my 50kB/s bandwidth is eaten up. Good for my downloads... but housemates don't like it.

What I want to know is... is the kB/s rating there supposed to be like a maximum, or is it just supposed to be a guideline? I do see the speed fall below 10kB/s quite often, but it's nothing like Azureus which will either sit exactly on or sit slightly below the limit I set.

I had a similar problem on 1.2_rc2 with speed capping but on the upload side (I have ADSL with 2MB/s down and 256kB/s up, so I rarely saturate the download rate), where the upload speed was consistently going over the limit. I installed the SVN version yesterday and that now adheres to the download limits, so my only advice is to either install the SVN version (see the FAQ on the site) or wait til 1.2 is released, which should include all the changes in the SVN version.

That's cool, I can wait if it's already fixed for the next release.

I too am seeing speed issues. Its going over my speed limit. That setting is for a total of all torrents running right? I have it set at 25k (I host web pages with the remaining bandwidth I have), and its jumping way past it, then throttling way back.

Ktorrent 1.2 download for debian from the website here.

It's worse than that though, I've often seen a *single* torrent jump above my speed limit even while other ones are still moving along. So it's not as if the limit is being applied per-torrent, rather that it's not being applied to inbound data at all.

Just to be clear in my case: Its outbound for me.

However, playing around a bit, I find that it obeys my up limit IF :

I stop all torrents. Set the speed. Close Ktorrent. Open Ktorrent, re start each torrent. Maybe the trick is to set your speed BEFORE you start the torrent.

I have been observing it for about 5 minutes, and if anything it is staying about 3k under my setting, which given overhead is perfect.

The upload limit should work fine, the download rate has some issues left to fix.

George wrote:The upload limit should work fine, the download rate has some issues left to fix.

Actually it does not, at least for me... the upload limit never worked (if not as an indication), and I update the SVN regularly (last time this morning). Now I have a 15K/s upload limit set, and ktorrent uploads in a range between 19 and 25
However, apart this problem, I really appreciate the work you're doing with ktorrent, it's by far the best torrent software for linux!

DelusionsMaster wrote:

George wrote:The upload limit should work fine, the download rate has some issues left to fix.

Actually it does not, at least for me... the upload limit never worked (if not as an indication), and I update the SVN regularly (last time this morning). Now I have a 15K/s upload limit set, and ktorrent uploads in a range between 19 and 25
However, apart this problem, I really appreciate the work you're doing with ktorrent, it's by far the best torrent software for linux!

The question is are you talking about the actual upload limit or the data upload limit (which we show in the GUI) ?

George wrote:The question is are you talking about the actual upload limit or the data upload limit (which we show in the GUI) ?

15 K/s is the limit I've set in the preferences: the GUI shows an average total upload speed of 13-14, whilst I can see, using an extern monitoring software (e.g. Nethogs, that shows the bandwitch for each active specific process), that ktorrent is actually uplading at 20 and more, and same thing says the other generic Ethernet interface bandwidth monitors I have (I've nothing else opened at the moment, so I know the speed they report is correct).

DelusionsMaster wrote:

George wrote:The question is are you talking about the actual upload limit or the data upload limit (which we show in the GUI) ?

15 K/s is the limit I've set in the preferences: the GUI shows an average total upload speed of 13-14, whilst I can see, using an extern monitoring software (e.g. Nethogs, that shows the bandwitch for each active specific process), that ktorrent is actually uplading at 20 and more, and same thing says the other generic Ethernet interface bandwidth monitors I have (I've nothing else opened at the moment, so I know the speed they report is correct).

I need to find some time to implement a limit for all packets (not just data).

This issue means a lot to me. I will have to monitor the traffic. I expected that to be a total of all traffic generated in the outgoing connection. And unless I follow my method, the upload data isnt capped anyways.

Thanks for looking at this issue, and I agree, this is great software for KDE and for Linux.

Left Ktorrent on for a few hours while I was away from the computer, and found it maxing out my connection again. I left it on overnight and same thing. Its ignoring my upload max setting. If I am working at the computer it doesn't seem to do it, now its happening if I leave it alone for more then an hour.

westyvw wrote:Left Ktorrent on for a few hours while I was away from the computer, and found it maxing out my connection again. I left it on overnight and same thing. Its ignoring my upload max setting. If I am working at the computer it doesn't seem to do it, now its happening if I leave it alone for more then an hour.

Strange, are you still on 1.2 ? Have you tried the latest from SVN yet ?

I did some more testing with upload and came to some interesting conclusions. It seems that the protocol overhead (other packets then data) is between 0.5 KB/s and 1.0 KB/s with a short peak of 2.0 KB/s. Even when downloading at speeds > 500 KB/s

So it seems that the other overhead is due to connection attempts (inbound and outbound). I'm gonna try limiting this number to something like no more then 10 at the same time.

George wrote:So it seems that the other overhead is due to connection attempts (inbound and outbound).

Might be caused by many bitcomet(and based) peers in a swarm. It sometimes has this attitude where it disconnets and reconnects like it's on ketamine, "when it's doesn't get what it wants". (i don't like this bitcomet client, really annoying...)