If lucky then one of the 4 different stable qBit installers option will load qBit faster, have to open and exit qBit twice, otherwise not a fair test. Enabling experimental SQL database should speed up opening qBit, but it's size grows way too big that it's better to try to be patient and stick with fastresume files. Some NVMe drives don't have heatsinks, then they can overheat, throttle and become slow, some even need a newer firmware update to avoid bad health issues. If you got NVMe, then loading torrents shouldn't take too long, unless you got many thousands of them or if previously had too old qBit version. In qBit v4.6.0RC2 advanced settings the current new defaults are Tracker timeout from 5 to 2 seconds and File Pool size from previous 5000 got changed to new low 100, very old versions had it only low 40. So I wouldn't be surprised if qBit installers with latest Qt or libtorrent code changes continue to cause more issues. Stable and unstable version installers quite often include latest dependencies, but development builds not always do so, so very often not enough proper tests are done before a new release, so I can't consider any qBit installers for Windows stable, even news page mentions many regressions or a need to revert versions of some dependencies. Just installing again won't reset settings, so many users are stuck with outdated or bad settings, some newer defaults might not be as good either and you don't even need to install qBittorrent to test latest fixes if really wanted to. If previously installed qBittorrent version loads everything quicker, then you could post your issue in GitHub, maybe someone there can confirm or fix this regression.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |