Rerun the benchmarks against the current tree - #31
Merged
Conversation
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
1 participant
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.
Every number in benchmarks/README.md re-measured on the tree that will ship as 0.2.0, same protocol as before. The scheduling-step and shape-sweep numbers barely moved; the single-process explorer got a touch faster than the 0.1.0 recording despite the per-delivery trace events; the 100k-seed campaign now takes just over six minutes rather than under, and the README and changelog claims move with it. The ablation density table came back byte-for-byte identical, including the two seeds where the missing idempotency key surfaces as a convergence failure.