Skip to content
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

limit parallel checking of torrents #139

Closed
milahu opened this issue Jun 17, 2024 · 2 comments · Fixed by #189
Closed

limit parallel checking of torrents #139

milahu opened this issue Jun 17, 2024 · 2 comments · Fixed by #189

Comments

@milahu
Copy link

milahu commented Jun 17, 2024

currently there seems to be no limit, all torrents are checked in parallel

cpu load is about 25% when checking 20 torrents in parallel
so this is just slow, not causing too much cpu load

libtorrent has the setting hashing_threads

aka: limit number of checking threads

@milahu milahu changed the title limit number of hashing threads limit parallel checking of torrents Jun 17, 2024
@ikatson
Copy link
Owner

ikatson commented Jun 19, 2024

There's probably a limit - the number of tokio IO worker threads. It's used for other things too though like writing to disk.
It's configurable from command line too: https://github.com/ikatson/rqbit/blob/main/crates/rqbit/src/main.rs#L105

Does that help?

@ikatson ikatson closed this as completed Aug 15, 2024
@milahu
Copy link
Author

milahu commented Aug 15, 2024

tokio IO worker threads

too generic. hashing threads produce more CPU load

in this case, serial processing is better, because checked torrents are ready for seeding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants