Since 4.3.7. Qbit has become useless for 2 reasons, first, it got a big RAM leakage problem (70% usage in a 32 GB system) and got lower UL speeds (10-20% of what 4.3.6. managed) but same or higher HDD usage, and second the Disk cache setting simply disappeared. In Task Manager, of course, Qbit RAM usage is ridiculously low (like 200 mb).
It looks exactly like uTorrent RAM leakage problem that they refused to acknowledge and solve and the main reason I switched 3-4 years ago to Qbit.
Meanwhile 4.3.6. works just fine, it has Disk cache setting (4000 mb) and everything is just fine. Coalesce reads and writes are on.
RAM leakage since 4.3.7
Re: RAM leakage since 4.3.7
Are you sure that the storage you are downloading to is working OK?
Back in the days, I'd seen countless people complaining about ram problems, and in the end, it was always their hardware.
Not just a storage issue per se. Raid controller, storage driver, anti-virus software, all sort of stuff can cause issues.
We always spend days, sometimes weeks troubleshooting.
https://docs.microsoft.com/en-us/sysint ... nals-suite
You can use "rammap" software from this to see what exactly eats up ram.
My qBittorrent eats 4,060K of ram (4.3.9 after hours of runtime.)
Back in the days, I'd seen countless people complaining about ram problems, and in the end, it was always their hardware.
Not just a storage issue per se. Raid controller, storage driver, anti-virus software, all sort of stuff can cause issues.
We always spend days, sometimes weeks troubleshooting.
https://docs.microsoft.com/en-us/sysint ... nals-suite
You can use "rammap" software from this to see what exactly eats up ram.
My qBittorrent eats 4,060K of ram (4.3.9 after hours of runtime.)
Re: RAM leakage since 4.3.7
The problem with libtorent 2 (that was adopted since 4.3.7) is dropping the custom disk cache, which especially made reading (writing also) depend on Win OS cache only, which is bad even on Win 11, and the effect is dramatically reduced upload speeds and RAM leakage. Obviously, if OS cache is disabled speeds are reduced even further. For the life of me I don't understand this change for which Qbit devs are not responsible and that cannot be corrected.
Now with Qbit 4.4.1/libtorrent 2 I have maximum 6-7 MBs upload speed per HDD, the drive being 100% active, while with 4.3.6/libtorrent 1, and disk cache being set to 4000 MB (same torrents etc) I have >20 MBs with the drive being 50-70% active. In the latter situation also after 1 hour or so RAM usage on my 32 GB machine gets higher than 50%, even if TaskManager shows like 200 MB for Qbit.
I realize many users may not be affected by this as many have 100 mbs download connections and probably upload speeds even lower., but I have a full duplex Gigabit connection and I could get 10 Gigabit for 10 bucks a month. And that could make sense only if I'm staying on 4.3.6.
Now with Qbit 4.4.1/libtorrent 2 I have maximum 6-7 MBs upload speed per HDD, the drive being 100% active, while with 4.3.6/libtorrent 1, and disk cache being set to 4000 MB (same torrents etc) I have >20 MBs with the drive being 50-70% active. In the latter situation also after 1 hour or so RAM usage on my 32 GB machine gets higher than 50%, even if TaskManager shows like 200 MB for Qbit.
I realize many users may not be affected by this as many have 100 mbs download connections and probably upload speeds even lower., but I have a full duplex Gigabit connection and I could get 10 Gigabit for 10 bucks a month. And that could make sense only if I'm staying on 4.3.6.
Re: RAM leakage since 4.3.7
As far as I am aware, only 4.4.0 was built using libtorrent 2.
4.3.9 still uses v1 branch.
If you check: https://www.qbittorrent.org/news.php
It says at 4.4.0: FEATURE: Support for v2 torrents along with libtorrent 2.0.x support (glassez, Chocobo1)
4.3.9 still uses v1 branch.
If you check: https://www.qbittorrent.org/news.php
It says at 4.4.0: FEATURE: Support for v2 torrents along with libtorrent 2.0.x support (glassez, Chocobo1)
Re: RAM leakage since 4.3.7
qBittorrent 4.3.9 with no torrents loaded, on my machine (Windows 7 Sp 1 32bit) uses 2,12 MB of ram according to Windows Task Manager. But Process Hacker shows that qB is actually using 22,73 MB of ram. This means Windows Task Manager doesn't report all the used ram.Peter wrote: Tue Nov 02, 2021 12:03 pm My qBittorrent eats 4,060K of ram (4.3.9 after hours of runtime.)
Re: RAM leakage since 4.3.7
You can use Rammap to see the details: https://docs.microsoft.com/en-us/sysint ... ads/rammap