Repository navigation
feat: publish reproducible million-row temporal join measurements - #14
Merged
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
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.
PITBridge had detailed correctness evidence but no reproducible large-workload measurement. This adds an isolated-process scalar benchmark with a fixed 20-observation / 4-decision shape, late revisions, tombstone fallback and TTL. Every trial checks all status counts, compares eight complete entities with the independent oracle, and records timings, whole-process RSS, environment, source hashes and the complete output digest.
Three trials at each size are published: 100,000 observations / 20,000 lookups at 2.875 s median; 1,000,000 observations / 200,000 lookups at 31.130 s median and 1.064 GiB peak whole-process RSS. All repetitions at each size agree on the output digest. The docs distinguish generation time, join time, whole-process memory, sample-oracle coverage and unmeasured rolling/online workloads. CI exercises the runner without unstable speed assertions.
Validation: 94 unittest cases pass, including isolated subprocess determinism and late correction/deletion/TTL behavior.