You are not logged in.
I was using µtorrent on windows and it seems to work in wine as well, more or less, using too much CPU and freezing now and then. So I switched to ktorrent and everything was working seemingly fine, except for uploading.
I have left the default values for the queue manager and contrary to µtorrent, I don't see it uploading most of the time. And when it does, it's only about 15 out of 60kb/s. µtorrent used all of the allotted 60kb/s after running for about 15minutes.
The ports are opened in iptables and forwarded in my router, so it shouldn't be a networking issue. I also made sure to restart the pc so that there are no leftover port binds from µtorrent.
I can also see seeds trying to connect to me even though I'm a seed myself. Shouldn't this happen at all?
By the way, is ktorrent development dead? The site linked on the wiki, ktorrent.org, seems to be offline and the last version seems to be more than a year old.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
Did you test both utorrent and ktorrent with the same torrent? Because it could simply be a case of more seeds and less leechers.
By the way, the ktorrent package lists the follwing website as the URL: http://ktorrent.pwsp.net/
Last edited by x33a (2014-07-28 12:26:57)
Offline
I actually loaded all torrents I had in µtorrent (about 40) to ktorrent and let it run for a day, so it shouldn't be this. µtorrent has the same queue settings when it comes to active torrents/seed slots, and manages to upload "all the time".
Thanks for pointing out, I found that other site before as well, but half of the link on there still point to the ktorrent.org site... and it seems pretty dead otherwise.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
Can you try increasing or decreasing the upload speed limit in ktorrent and see if the actual speed changes accordingly.
For example, set the upload limit to 100 KB/s, then see if it goes beyond 15 KB/s or not. Similarly, set it to 10 KB/s, and see if it reaches 10 KB/s or remains at a much lower speed.
Offline
It was set to "no limit", setting it to 60kb/s doesn't change anything. I also just noticed the UDP tracker port seems to reset itself to a random port, even though I set it to be same as my tcp port? Though changing the port (and verifying it works on it) still doesn't change the upload behavior. Just a comparison: µtorrent gets the first connection within the first minute, and begins seeding at ~30kb/s, which then beings to raise until it maxes out my connection (if it's free). Ktorrent gets a connection pretty fast too, but they only upload at ~10kb/s and never get higher.
I noticed something was wrong because usually I am able to seed back all the files I downloaded during the day overnight. But after a day with ktorrent, my ratios are still at 0.01-0.07...
I also tried using µTP as main protocol (currently TCP again) but that doesn't seem to change anything.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
Hmm.. I guess you'll need to report a bug upstream. But since you believe the development to be dead (I didn't check it myself), you might want to switch to another torrent client altogether. I suggest you give qbittorrent a try.
Offline
I've looked at their forums and someone was facing the same issue way back and the last post was in January 2014, noting that it has been 3 years since the issue started and that it still persists. This kind of proves development is pretty much dead to me. Oh yes, I forgot to mention the upload is normal while the torrent is downloading, but once it finishes, everything stops and upload is very sluggish.
Anyway, qbittorrent was actually my first choice on linux since it offers everything utorrent does. However, there is a currently unresolved bug which results in qbt paving over existing files silently in multiple situations (for example when switching clients or moving files). And that's what it did once I tried to switch from µtorrent. Luckily I didn't lose much, but I will just bear with high cpu usage from utorrent for now.
Last edited by Soukyuu (2014-07-28 19:13:21)
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
It seems only some people have trouble with uploading in ktorrent.
Perhaps give transmission a go. It supports everything bittorrent offers and can run as a daemon, with many clients available, including a qt5 one with a non-utorrent-like interface and a qt4/gtk2 one with an utorrent-like interface (transmission-remote-gui).
Offline
Thanks for the suggestion, but I'm using RSSfeeds to pull my content and the way transmission does it looks complicated to me. I also tried deluge, but it also suffers from the same behavior as qbt, as it is based on libtorrent as well.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
Thanks for the suggestion, but I'm using RSSfeeds to pull my content and the way transmission does it looks complicated to me. I also tried deluge, but it also suffers from the same behavior as qbt, as it is based on libtorrent as well.
For Deluge anyway I noticed something like this too. But then I realized that "Rate Limit IP overhead" was checked and that takes into account the estimated protocol traffic in to any IP limits. So what was happening was that when I was downloading too it generated significant upstream protocol traffic leaving very little left for the uploads/seeding. I don't know if this explains your issue or not but figured that I would mention it just in case.
Also check that your ISP connection isn't having issues. I had strange upload issues on torrents and sometimes when uploading to Youtube. I discovered that my upstream signal strength on my cable modem was at the border line for being within specifications and sometimes it would cause issues with the upstream connection. One of the things I saw was my torrents all going to 0.0 kbps upload randomly. I thought it was my ISP throttling until I figured it out. If on cable usually you can access the modem at an ip like 192.168.100.1 and then see the diagnostics page for the signal strength.
Last edited by davidm (2014-07-30 01:15:31)
Offline
Shouldn't be a connection issue, as I'm able to down- and upload with anything but ktorrent. What you describe is a bandwidth issue, btw. It's normal for the upload to go down when you're downloading at full speed, especially on an ADSL connection like mine, where upload is only a fraction of my download bandwidth. For ktorrent, it's the other way around: I have higher upload when I'm downloading. It's like the client is set to only seed while downloading. I also found out some private trackers have blocked it, so it looks like the behavior I'm having is known for a longer time.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline