libtorrent: Implement two hash queue threads #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stickz
added a commit
to stickz/docker-rtorrent-rutorrent
that referenced
this pull request
Jul 16, 2024
## Version 5.4 Release This release includes two hash threads instead of one to better split the load between multiple threads. For instance, instead of 30% on a single thread it will execute two threads with 15%. Half the downloads are assigned to one thread and the other half to the other thread. UDNS now works as intended. A build issue is fixed for debugging. A handshake build mount is added for later for multi-threading support. ## What's Changed * libtorrent: Implement two hash queue threads by @stickz in stickz/rtorrent#28 * libtorrent: Add handshake bind mount by @stickz in stickz/rtorrent#29 * libtorrent: Add UDNS to configure.ac by @stickz in stickz/rtorrent#32 * libtorrent: Fix instrumentation debug regression by @stickz in stickz/rtorrent#33 **Full Changelog**: stickz/rtorrent@v5.3-0.9.8-0.13.8...v5.4-0.9.8-0.13.8
This was referenced Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can evenly divide the downloads between two different HashQueue objects. This allows us to create anther disk thread to schedule the CPU load more evenly between multiple processor cores. A common scenario is for 30% of the CPU usage to be allocated for hashing. This pull request would split that load between two threads at 15% when multiple downloads are active.