Repository navigation
profile harness: parallelise roles, hoist message generation, add PROFILE_ROLE - #18
Merged
Merged
Conversation
…FILE_ROLE the driver looped over clients, envelopes and servers serially with only the small per-call fan-out inside, so most rayon workers idle-spun and the profile was dominated by that and by the driver's own message rng. client rounds now run concurrently across clients on forked seeds, each server unseals and sums its inbox in parallel with the others, messages are drawn once in setup, and PROFILE_ROLE repeats one party's work in isolation.
This was referenced Nov 5, 2026
noot
marked this pull request as ready for review
November 5, 2026 21: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.
Fixes
examples/profile.rsso clients, server unseals and server rounds run in parallel instead of serially, messages are drawn once outside the timed loop, andPROFILE_ROLE=client|server|recipientrepeats only one party's work.On 32 threads a round drops from 1.39 s to 0.30 s and idle rayon time from 30% to 2%. No library changes.
#15 is stacked on this.