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

Forced torrents re-checks or changes location without one-at-a-time queueing #8247

Open
Aaron432 opened this Issue Jan 9, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@Aaron432

Aaron432 commented Jan 9, 2018

When I have multiple torrents set as "Force Resume" (f.e. seeding with "forced" mode) and I want to recheck/rescan all those torrents, they all rechecks simultaneously, without queue'ing one at a time.
To do such scan, I need to disable "forced" mode or pause those torrents and then they queue-rechecks properly.
Same thing applies when I want to move such forced torrents from one hard drive to another.
It causes huge load on drives, because all torrents are being read/write simultaneously and there's no way to stop it once it starts.
In this case also pausing or disabling "[F]" mode allows for a normal location changing.

OS: Mint 18.1 x64
Currently on: 4.0.3.99201801030134-6257-d5acd1fubuntu16.04.1
I've encountered this issue in previous builds as well, but I don't think I've had it on version 3.3.

@githubuserthatsright

This comment has been minimized.

Show comment
Hide comment
@githubuserthatsright

githubuserthatsright Jun 23, 2018

Not being able to queue "set location" commands happens for 4.1.1 32 bit qbittorrent on Windows 10 64 bit as well.
It is atrocious; if you are moving even two torrents at the same time, it will slow down transfers well over 50% on hard disks. It is not a lot to ask - simply enable queueing of relocation (and recheck - same issue there) tasks.

githubuserthatsright commented Jun 23, 2018

Not being able to queue "set location" commands happens for 4.1.1 32 bit qbittorrent on Windows 10 64 bit as well.
It is atrocious; if you are moving even two torrents at the same time, it will slow down transfers well over 50% on hard disks. It is not a lot to ask - simply enable queueing of relocation (and recheck - same issue there) tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment