search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
26.95k stars 3.88k forks source link

QBT simultaneous checks hash on all selected torrents, depsite conf HashingThreadsCount=1 #21127

Open Zenya393 opened 1 month ago

Zenya393 commented 1 month ago

qBittorrent & operating system versions

qbittorrent v4.6.5 Qt: 6.6.3 Libtorrent: 2.0.10.0 Boost: 1.84.0 OpenSSL: 3.3.1 zlib: 1.3.1 Operating System: Linux (via docker)

What is the problem?

QBT will simultaneous hash check all selected torrents, and not honor the maximum number of files to perform a hash check.

Since I don't have a lot of compute (but multiple drives), I want QBT to only hash check one file of time. I want the other files to be queued. This way my selected torrents aren't taken offline to perform the hash check. Also, if I select 1000 torrents to hash check, all 1000 will compete for resources.

Steps to reproduce

  1. Select a list of torrents from WebUI.
  2. Right-click and select "force recheck".
  3. QBT will being checking all the select torrents at the same time.

Additional context

No response

Log(s) & preferences file(s)

Session\HashingThreadsCount=1

HanabishiRecca commented 1 month ago

Session\HashingThreadsCount does not do what you think.

You need Session\MaxActiveCheckingTorrents option instead. It is also available as Settings > Bittorrent > Max active checking torrents in the GUI/WebUI.

Zenya393 commented 1 month ago

Session\HashingThreadsCount does not do what you think.

You need Session\MaxActiveCheckingTorrents option instead. It is also available as Settings > Bittorrent > Max active checking torrents in the GUI/WebUI.

I also have this setting in my configuration:

Session\MaxActiveCheckingTorrents=1

HanabishiRecca commented 1 month ago

Did you press Force Start on that torrents? If they have [F] tag in the status, it ignores restrictions.

Zenya393 commented 1 month ago

Yes, I did press Force Start on the torrents, so the torrents were in forced download/upload.

So what I should have? 1) Tag all the torrents as forced upload. 2) Un-force the torrents. 3) Force re-check, which will now honor and queue the torrents for rechecking according to MaxActiveCheckingTorrents. 4) After the checks are complete, go to the tagged torrent and force them back to upload.

HanabishiRecca commented 1 month ago

Yes, I did press Force Start on the torrents

Then that's the intended behavior.

go to the tagged torrent and force them back to upload.

Force option is not supposed to be used like that. Don't do that. Just tune Torrent Queueing limits to fit your needs instead. Or disable it completely if you want everything always working.