I’ve been using Manjaro as my daily driver for a couple of months now, and something I’ve noticed is that torrent speeds have been very slow compared to those I used to have when using Windows 10.
Before anyone mentions it: Yes, I am connectable, all of my ports are being forwarded, etc, etc, etc. It has nothing to do with that. I have a 200 mbps connection (up & down), so speed shouldn’t be an issue.
I’m using pretty much the same setup I’ve been using on Windows which is qBit with exactly the same settings. Downloading a 300 meg file would usually take a couple of seconds, but in Manjaro it will take over 5 minutes and sometimes even over 10. I also used to get pretty good upload ratios with all my downloads. If I downloaded a 500 meg file, I could easily get a ratio of over 30 if I left the torrent seeding all day. Now, I barely even break a ratio of 5 when seeding a file of a similar size for the entire day.
What settings can I change to upload and download torrents more efficiently with qBit on Manjaro?
Weird, i don’t have that kind of issue, and i’m using qbittorrent too.
I suppose you converted your Windows computer to Manjaro? So same same hardware?..
Please read this: How to provide good information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
Not helping but there is no difference between Manjaro and Windows on my side either. I use(d) same on Windows. This could simply be the torrent file itself.
Some detective work can guide others to the real culprit,
Are the torrents downloading to the same physical drive and/or partition?
What are your settings in qBittorrent? (Especially in regards to DHT, PEX, encryption/obfuscation, anonymous mode, disk preallocation)
What speeds do you get if you try with aria2c on a known fast torrent? (aria2c https://path/to/download.torrent) (The package name is aria2 if it’s not currently installed)
What speeds do you get with qBittorrent on a known fast torrent if you save it to a ramdisk?
To create a temporary ramdisk, make sure it is large enough to hold the entire download:
You can later unmount the ramdisk and remove the directory when you’re done testing.
Keep in mind a ramdisk consumes RAM. So the above example will immediately consume 2GB of RAM until you unmount it.
When prompted to save the download in qBittorrent, browse to /mnt/torrent-test/
These above tests might clue someone into what might be the culprit if you’re consistently seeing slower speeds under Manjaro vs Windows 10, using the same version of qBittorrent.
For comparison, here is a sample of the dynamic output from aria2c when downloading the LibreOffice torrent to the ramdisk:
so read this but this is unrelated to your current problem; just ensuring you don’t get freezes in the future.
You have NTFS HDDs mounted so the mount parameters of these are crucial if you want to attain a high speed, and you seem to be using automounts: Are any of these automounts in use for qBitTorrent?
Another thing to rule out is to check (or force set) the option in your network card to “Auto Negotiate”. Many systems default to “Ignore”. Change this to “Automatic”.
If it hasn’t been set previously, might as well Apply and reboot your computer to further assess your download speeds. (I believe a reboot / reloading of the driver is required for the change to take effect.)
However, I wrote the above steps as a process of elimination, since it might clue others that this might be one or the following at fault,
physical drive
filesystem
software application
unfriendly settings for Linux / native filesystem
network card and/or driver
UPDATE: Just to confirm, it does indeed require a reboot (or reloading the module) for the change to take effect.