Conversation
03c7c3b to
a3efc57
Compare
12bbcc8 to
1290e3a
Compare
1290e3a to
bfa1b57
Compare
Member
|
We have a benchmark like that in one of the tests (conditionally compiled, off by default). It's a bit misleading because it's always hitting the same cache line and will always hit in the branch predictor. Last time I did some deep analysis, it was taking around 4 cycles on a Haswell chip to go through the entire message-send machinery. That drops off sharply if we miss in the L1 for the dtable. Running benchmarks in CI on GitHub Action Runners is not very useful because they'll end up on a random VM (where CPUID lies and may pretend to be an older core than it is), so may vary hugely with no code changes. |
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.
No description provided.