[quote="KitKat"]
/e2: A possible suggestion would be disc useage/overload causing the slow transfer cap?
I believe qbittorent "sanity checks" pieces alot more frequently than utorrent/qbittorent.
If you're using a small piece size in a single seed/peer case it can lead to a slower transfer rate.
[/quote]
So far, I was convinced that libtorrent takes over that part, which is why I was wondering since Deluge (which uses libtorrent, too) does reach way higher speeds on LAN.
For this test, I am using an archive of the size 562MB. The torrent, created with Deluge, has a piece size of 1MiB, thus has 563 pieces.
What I analysed: Speeds, HDD usage and special things that may have happened, plus possible additional information (if I could get some)
Router model is a Fritz!Box 7330, using channel 4 at 2.4GHz (thus no influence by other WiFis in my neighbourhood), 802.11n @ 72MBit/s on the laptop.
// This reply will get edited, as soon as I get more results, or I forgot some infos.
How all clients are set up (yes, all of them):
- no speed limits
- used ports are all forwarded, and only used once per try
- Global maximum number of connections: 200
- Maximum number of connections per torrent: 30
- Global Maximum number of upload slots: 8
- Maximum number of upload slots per torrent: 2
Deluge 1.3.12 to x
Deluge 1.3.12 to qBittorrent 3.3.4 / 3.4.0alpha: Speeds around 1-1.3MiB/s; Read Cache Hits: 95,39 // HDD usage peaks around 2MB/s to 1 MB/s to 0MB/s, and repeating.
Deluge 1.3.12 to µTorrent 2.2.1: Speeds around 2-2.5MB/s, sometimes going down to 1.5MB/s, but not lower. // HDD usage peaks constantly around 2-3MB/s.
Deluge 1.3.12 to µTorrent 3.4.6: Speeds around 3-3.5MB/s // HDD usage peaks around between 0MB/s to 7MB/s
Deluge 1.3.12 to Deluge 1.3.12: Speeds around 3-3.8MiB/s // HDD usage peaks around between 0MB/s to 7MB/s
What I mean with "peaks":
https://i.imgur.com/4MOlVmd.png
qBittorrent 3.3.4 / 3.4.0alpha to x
qBittorrent 3.3.4 / 3.4.0alpha to qBittorrent 3.3.4 / 3.4.0alpha: Speeds around 780KiB/s-1.3MiB/s; Read Cache Hits: 50,00 // HDD usage peaks around 2MB/s to 1 MB/s to 0MB/s, and repeating.
qBittorrent 3.3.4 / 3.4.0alpha to µTorrent 2.2.1: Speeds around 1.4-1.6MB/s, sometimes going down to 1.5MB/s, but not lower. // HDD usage peaks constantly around 2-3MB/s.
qBittorrent 3.3.4 / 3.4.0alpha to µTorrent 3.4.6: Speeds around 2.7-3.4MB/s // HDD usage peaks around between 0MB/s to 7MB/s
qBittorrent 3.3.4 / 3.4.0alpha to Deluge 1.3.12: Speeds around 780-1.3MiB/s // HDD usage peaks around between 0MB/s to 2MB/s
Note: When stopping the transfer either of the leeching client (Laptop) or the seeding client (Desktop), it takes way more time to reconnect and restart the transfer than with Deluge.
µTorrent 3.4.6 to x
µTorrent 3.4.6 to qBittorrent 3.3.4 / 3.4.0alpha: Speeds around 250KiB/s-550KiB/s; Read Cache Hits: 83,07 // HDD usage around 1MB/s
µTorrent 3.4.6 to µTorrent 2.2.1: Speeds around 3.5-3.8MB/s // HDD usage peaks constantly around 2-3MB/s.
µTorrent 3.4.6 to µTorrent 3.4.6: Speeds around 2.7-3.4MB/s // HDD usage peaks around between 0MB/s to 7MB/s
µTorrent 3.4.6 to Deluge 1.3.12: Speeds around 2.9-3.4MiB/s // HDD usage peaks around between 0MB/s to 2MB/s
µTorrent 2.2.1 to x
(This one is really weird.)
µTorrent 2.2.1 to qBittorrent 3.3.4 / 3.4.0alpha: Speeds around 450KiB/s-850KiB/s; Read Cache Hits: 75,00 // HDD usage around 1MB/s
µTorrent 2.2.1 µTorrent 2.2.1: Speeds around 3.4-3.5MB/s // HDD usage peaks constantly around 2-3MB/s.
µTorrent 2.2.1 to µTorrent 3.4.6: Speeds around 3.3-3.7MB/s, connection drops when reaching this peak. // HDD usage peaks around between 0MB/s to 7MB/s
µTorrent 2.2.1 to Deluge 1.3.12: Speeds around 650KiB/s-900KiB/s // HDD usage peaks around between 0MB/s to 2MB/s
Instead of Desktop > Laptop, I did the same the other way around, with the same results.
TL;DR:
x to qBittorrent is slow, the most times.