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.
Summary
Adds the TailCache 06 result pipeline for the heap-pressure crossover study.
This PR separates latency, throughput, and GC/allocation measurement into distinct JMH runs, retains the raw evidence needed for auditability, and joins matching conditions into analysis-ready JSON/CSV output.
What changed
Validation
Final smoke validation and raw reconciliation passed at:
with a clean working tree.
The branch has advanced since that smoke only through documentation changes; benchmark/result code remains unchanged.
Verified:
gitDirty=false, Java 21, JMH 1.37, Caffeine 3.2.4, and Chronicle Map 2026.1Important scope note
This validates the result pipeline, not the smoke benchmark values as reportable research results.
The next milestone is the trustworthy crossover harness: environment capture, harness-floor measurement, warmup/JIT stability, pause-sensitive latency validation, and a dedicated GC-pressure workload without a Chronicle Java-heap shadow payload bank.