feat: add configurable cache statistics and latency snapshots - #51
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.
Summary
Add
RuntimeOptions::statsandCache::stats_snapshot()so applications can collect complete request outcomes and cumulative latency distributions independently of the legacy statistics switch. L1 hits, L2 lookups and mutations each support disabled, full or sampled timing. L2 timing starts at L1 miss, allowing full L2 collection without clocks on L1 hits; engine timing covers read/write/reclaim requests from slot reservation through completion.Recorders use bounded atomic stripes charged to managed memory. Structured snapshots expose timing scope, sampling mode, bucket counts, duration sums and validity; applications own metric conversion and export. Fully specified
RuntimeOptionsliterals need astatsfield or a struct-update default. Includes a runnable snapshot example, benchmark controls and regression coverage for accounting, timing boundaries, cancellation and concurrency.Validation:
cargo x check,cargo x test, andcargo x lintpassed. The io_uring library also cross-compiles forx86_64-unknown-linux-gnu; Linux runtime execution was not tested locally.