Set OMP_NUM_THREADS for flow2supera - #94
Open
mjkramer wants to merge 2 commits into
Open
Conversation
When flow2supera runs DBSCAN, it spawns a bunch of threads. The threading doesn't seem to benefit performance, and it greatly limits the number of parallel flow2supera processes that can be run before everything slows to a crawl. Setting `OMP_NUM_THREADS` to 1 doesn't slow down flow2supera much (if it all) in my experience, and allows every core to be used efficiently for its own flow2supera process.
mjkramer
marked this pull request as ready for review
July 17, 2026 02:47
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.
When flow2supera runs DBSCAN, it spawns a bunch of threads. The threading doesn't seem to benefit performance, and it greatly limits the number of parallel flow2supera processes that can be run before everything slows to a crawl. Setting
OMP_NUM_THREADSto 1 doesn't slow down flow2supera much (if it all) in my experience, and allows every core to be used efficiently for its own flow2supera process.