qBittorrent: 4.4.1 x64
Operating system: Windows 11
Qt: 5.15.2
libtorrent-rasterbar: 2.0.5.0
RAM: 16GB
Task: upload only
====================================================
When using Transmission, the hard disk is read every 5~10 seconds.
As shown below:
After switching to qBittorrent, at the same upload speed, the hard disk read becomes very frequent, and there is not much data read each time. I checked a lot of information on the Internet, and repeated debugging was unsuccessful.
This seriously affects other processes: verifying files at the same time, or downloading at the same time.
I have repeatedly adjusted the values of send_buffer_low_watermark and send_buffer_watermark, but I can't reduce disk reading.
I found that the total buffer size, no matter how it is adjusted, is only 10~20mb at most, and it is impossible to allocate a 1gb read cache like Transmission.
qBittorrent reads the hard disk too frequently
Re: qBittorrent reads the hard disk too frequently
On qBitTorrent's github for issues, I spotted a similar post about too many reads:
Intensive IO read when seeding
https://github.com/qbittorrent/qBittorrent/issues/14844
And also this, which could be part of the underlying problem:
Performance warning: max outstanding piece requests reached
https://github.com/qbittorrent/qBittorrent/issues/16668
HOPEFULLY, both issues will be greatly reduced or completely fixed by the next non-beta release of qBitTorrent.
Intensive IO read when seeding
https://github.com/qbittorrent/qBittorrent/issues/14844
And also this, which could be part of the underlying problem:
Performance warning: max outstanding piece requests reached
https://github.com/qbittorrent/qBittorrent/issues/16668
HOPEFULLY, both issues will be greatly reduced or completely fixed by the next non-beta release of qBitTorrent.
Re: qBittorrent reads the hard disk too frequently
ever find a solution to this? boy oh boy is information slim pickings out there.
I see the same behavior using lib2 builds. Virtually no buffer is used, and downloading is perpetual epic write-cache overload. thrashes the drive to death and speeds are just... all but non existent.
a simple swap to 1.x build and its all business as usual again.
has to be something im missing in regard to how libtorrent 2 functions, seems its not caching anything even when a ton of ram is given to it.
I see the same behavior using lib2 builds. Virtually no buffer is used, and downloading is perpetual epic write-cache overload. thrashes the drive to death and speeds are just... all but non existent.
a simple swap to 1.x build and its all business as usual again.
has to be something im missing in regard to how libtorrent 2 functions, seems its not caching anything even when a ton of ram is given to it.