-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abnormally slow IO performance on CIFS network share #19407
Comments
Try testing with libtorrent 1.2.19 |
Big improvement. Used |
When using libtorrent 1.2.19 my page cache just fills up due to the network share not being fast enough. I configured the following sysctl options, now the system just hangs for a few seconds, but qBittorrent never recovers speed:
|
Why SMB in lieu of NFS? |
My storage provider sadly only supports SMB (Hetzner Storage Box). |
I'm now on a box with 2x 8 TB HDDs (HGST HUH721008AL) in RAID 0 and no longer experience a noticeable performance impact, contrary to some reports of others ( arvidn/libtorrent#7480 (comment) ) |
Anymore progress on this ? |
Sadly not. And I don't think there will be, as this seems to be a quite niche use case. But as this isn't caused by qBittorrent directly, I recommend using the issue in the libtorrent repo for further comments: arvidn/libtorrent#7480 |
Closing in favor of upstream libtorrent ticket. @constantins2001 can you ping this ticket if any upstream changes take effect ? |
qBittorrent & operating system versions
qBittorrent-nox: 4.5.4-r2 ARM64
Operating system: Ubuntu 22.04.2 LTS - Docker linuxserver/qbittorrent:4.5.4
Qt: 6.5.2-r0
libtorrent-rasterbar: 2.0.9-r2
What is the problem?
IO on mounted CIFS (SMB) network share are abnormally low.
This indicates qBittorrent has drastically slower speeds when moving downloads/downloading to network shares compared to a manual move operation.
Steps to reproduce
mount.cifs -o user=<XXX>,pass=<XXX>,cache=loose,actimeo=120,fsc //<URL>/<share> <mountpoint>
<mountpoint>
Additional context
I'll be happy to provide a full testing environment, just contact me directly.
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: