Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
levkk
reviewed
Nov 10, 2026
| bench = [] | ||
|
|
||
| [dependencies] | ||
| foldhash = { version = "0.2", default-features = false } |
Collaborator
There was a problem hiding this comment.
You could make it conditional, i.e., only if bench feature is enabled. Although LLVM will probably remove it anyway during compilation / dead code elimination.
Contributor
|
Metal bench (arm64) passed. All 475 measures within bounds.
Counters per txn
Microbench: all 462 measures within bounds. Hot code per txn
pooler:
sharding-w2:
Logslb, microbench, pooler, sharding-w2, sharding-w8, verdict.json |
Contributor
|
Metal bench (x86) passed. All 475 measures within bounds.
Counters per txn
Microbench: all 462 measures within bounds. Hot code per txn
pooler:
sharding-w2:
Logslb, microbench, pooler, sharding-w2, sharding-w8, verdict.json |
This branch has not been deployed
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.
Follow up work to try to improve accuracy of microbench instructions in reference to #2003 seeing a +1.54% increase for a measure that shouldn't have been affected by that PR.
After some investigation, this seems to be because our LRU caches hash with foldhash, which builds a hash seed from code addresses (as a source of randomness). My guess is that this can change the order that we free cache entries in, and with that differs the work of all subsequent
malloccalls.Reference to their code that does this: https://github.com/orlp/foldhash/blob/77d8e3dae0d43abe65753e888b9e74efbe4ee3f7/src/seed.rs#L150-L156
Now, in the microbench, the LRU caches hash with a fixed seed (via
foldhash::fast::FixedState, which they recommend for determinism).This doesn't affect production builds.