Repository navigation
test: harden Stax latency evidence and MCP cancellation - #51
Merged
Merged
Conversation
fcostaoliveira
marked this pull request as ready for review
October 23, 2026 20:46
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.
Stax wait reports now expose whether scheduler records were observed, compare archived/reported counts, and state that an empty report does not establish no blocking. Older stored documents gain these diagnostics at query time without reimport. This follows native reduced-mode controls that produced CPU data while omitting scheduler records.
The Redis pilot retains individual PING monotonic start/end timestamps and RTT, reports baseline p99 variation, and treats missing latency evidence as inconclusive. New stdio protocol coverage cancels active and queued captures and verifies partial retention, child reaping, borrowed-target survival, no storage and continued responsiveness.
The measured follow-up includes exact paired values, binary/source hashes and isolated diagnostic patches. Five 30-second pairs gave +1,434.11% median paired PING p99 on pinned Stax with 0.34% throughput loss; a main-thread-only prototype gave +80.43% p99 with 0.20% throughput loss and lost thread/off-CPU coverage. Both failed the declared latency budget. Short prototype median passes did not survive longer measurement. No source workaround is selected automatically or adopted as a production fix.
M6 guidance also reproduces the pinned native comparison bug (299 synthetic markers reported as PET samples despite zero CPU samples), records fresh capture identity evidence, and provides explicit extraction commands for its pinned source example. Raw PMU scope remains distinct from per-process counters/CPI.
Validation:
Capture remains experimental. This VM study does not validate other platforms, hardware PMU access or a production overhead guarantee. Privileged M1/M6 Stax CPU acceptance remains pending.