Skip to content

fix(nargo): don't thread-bomb unnecessarily#16594

Closed
ludamad wants to merge 1 commit intomerge-train/barretenbergfrom
ad/nargo-no-thread-bomb
Closed

fix(nargo): don't thread-bomb unnecessarily#16594
ludamad wants to merge 1 commit intomerge-train/barretenbergfrom
ad/nargo-no-thread-bomb

Conversation

@ludamad
Copy link
Collaborator

@ludamad ludamad commented Aug 26, 2025

noir repo PR noir-lang/noir#9643, this is just getting in ahead of the next sync (unless noir team advises otherwise)

Previously, setting RAYON_NUM_THREADS was the workaround for running many nargos in parallel. However, to be able to run on a very large number of core machine like aztec's shared "mainframe" instance, there was easy low-hanging fruit.

This removes all the cases where threads allocated could have been >> threads used.

noir repo PR noir-lang/noir#9643

Previously, setting RAYON_NUM_THREADS was the workaround for running many nargos in parallel. However, to be able to run on a very large number of core machine like aztec's shared "mainframe" instance, there was easy low-hanging fruit.

This removes all the cases where threads allocated could have been >> threads used.
@ludamad ludamad requested a review from TomAFrench as a code owner August 26, 2025 18:17
@TomAFrench
Copy link
Member

Can we just update the pinned commit once the other PR is merged? This just immediately creates extra work in the sync to remove this patch.

@ludamad
Copy link
Collaborator Author

ludamad commented Aug 26, 2025

Sure! I wanted to decouple the process, but whatever is easiest

@ludamad ludamad closed this Aug 26, 2025
@ludamad ludamad deleted the ad/nargo-no-thread-bomb branch December 3, 2025 16:22
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 this pull request may close these issues.

3 participants