Repository navigation
Update Helidon startup and memory numbers for the jlink image - #352
Merged
Merged
Conversation
The reactive Helidon app now runs as a jlink image with an AOT cache instead of a native executable. I re-measured it with start.sh on an Apple M3 Max with 64 GB RAM, the same hardware as the other numbers: three warm-up runs, then five recorded runs.
Measured with memory.sh and a real access token on an Apple M3 Max with 64 GB RAM. Each number is the median of three runs.
mraible
changed the title
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.
The reactive Helidon app switched from a native executable to a jlink image with an AOT cache in #346, so its startup and memory numbers in
reactive/demo.adocwere stale. I re-measured both on an Apple M3 Max with 64 GB RAM, the same hardware as the existing numbers.Startup, using
start.sh helidonwith three warm-up runs and then five recorded runs:start.sh: 197, 197, 197, 198, 195, for an average of 196.8 ms (was 248.4 ms native).Memory, using
memory.shwith a real access token, as the median of three runs:Both tables now note that Helidon's numbers are for a jlink image running on the JVM, not a native executable.