test: add read-after-write latency measurement for #38#47
Open
0xlavar wants to merge 2 commits into
Open
Conversation
- Basic timing using TestEnv harness - Addresses the read latency after write opportunity - Provides baseline data (currently ~8µs) Refs: spool-labs#38
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
1 participant
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 an initial read-after-write latency measurement test using the TestEnv harness.
Motivation
Per the latest comment by @zfedoran on #38:
This PR provides a concrete baseline measurement (~8µs currently) as the first step.
Changes
measure_read_after_write_latencytest intest/src/lib.rsHow to Test
cargo test --package tape-test measure_read_after_write_latency -- --nocaptureHappy to expand this with real Tape Replay write + read operations or component-level timing based on feedback.
CC #38