Add a fetch-compute-concurrency option for toolkit#675
Merged
Conversation
Contributor
Contributor
|
Thanks for the PR - please add a change file under |
Contributor
Author
|
@ozgb change file added |
…tions Signed-off-by: chrispalaskas <chris.palaskas@gmail.com>
ozgb
approved these changes
Feb 23, 2026
gilescope
pushed a commit
that referenced
this pull request
Apr 8, 2026
m2ux
added a commit
that referenced
this pull request
Apr 23, 2026
Signed-off-by: Mike Clay <mike.clay@shielded.io>
m2ux
added a commit
that referenced
this pull request
Apr 23, 2026
Signed-off-by: Mike Clay <mike.clay@shielded.io>
This file contains hidden or 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
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.








Overview
I added an argument for the MN Toolkit which will limit the number of compute tokio tasks. The reason we need that is that we are already running the toolkit multithreaded, and each thread has to update the toolkit.db (which is another area of improvement). That leads to massive overburdening of the system.
🗹 TODO before merging
📌 Submission Checklist
🧪 Testing Evidence
Tested locally, indeed it fetches extremely slow with 1 compute worker.
Please describe any additional testing aside from CI:
🔱 Fork Strategy
Links