Reorder benchmarks to avoid impacting performance - #5529
Merged
Conversation
Signed-off-by: Jade Abraham <jade.abraham@hpe.com>
benharsh
approved these changes
Sep 3, 2026
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
2 participants
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.
Reorder the benchmarks so that 1trc is last instead of first.
After 1trc was added, there started to be some instability in some of the benchmarks runs for single node. This is suspected to be due to a single server state being perturbed by 1trc before other benchmarks that rely heavily on server state (eg stream)
See https://chapel-lang.org/perf/arkouda/chapcs/?startdate=2026/08/06&enddate=2026/09/03&graphs=streamperformance,1trcperformance,1trctime
This is not indicative of real world performance, but we want to maintain as clean as possible perf tests