Repository navigation
bench: add verified JVM release timing harness - #21
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.
Adds JVM runtime measurements for project-minigraf/minigraf#839: six common foreign binding round trips and eight preparation, registration, options, FactLog/LogWriter and storage cases. Every invocation validates actual values; storage cases reopen and compare contents. The source-build script verifies the pinned core, builds the local binding and runs oracle checks.
Validation on the dedicated bench: 44 Rust binding tests, binding/Gradle tests, three negative-control oracle tests, all 14 smoke cases, and three fresh JVM runs containing 420 validated samples. Fixed 512 MiB/G1, serial CPU+memory NUMA affinity, and before/after idle checks. Packaged native and installed jar hashes match the recorded build. Some cases vary substantially; no performance threshold or release acceptance is claimed.
Existing nightly benchmarks are unchanged. Full sanitized evidence and remaining dispositions are in the core bench/839-binding-evidence branch. This is source-build evidence, not published-package verification.