core/vm: specify concurrent tasks to 1 for bls msm precompiles #30358
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've discussed that these should not be performed concurrently. Unfortunately, even with specifying
NbTasks: 1
, the implementation still uses goroutines.Ultimately, it's unclear if we will use the current gnark MSM implementation, or there is some other MSM algorithm more amenable to single-threaded execution.
Overall, restricting
NbTasks: 1
decreases performance of the MSM precompiles by ~40% in the worst case on my machine. Executing benchmarks withNbTasks: 1
becomes marginally better whenGOMAXPROCS=1
is specified.Performance for random inputs, ran on my M2 MBP (from the benchmarks I've put together here):
Edit: Made a mistake. re-running benchmarks and will post them again.