Repository navigation
perf(route-cache): V5 passive SQL settlement and event-loop root-cause diagnostics - #843
Merged
Boym323 merged 10 commits intoOct 13, 2026
Merged
Conversation
…thout changing timeout or circuit
Boym323
marked this pull request as ready for review
October 13, 2026 08:04
Boym323
deleted the
perf/route-cache-v5-root-cause-attribution-20261013
branch
October 14, 2026 14:28
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.
V5.1 – Read-only route-cache DB latency attribution
V5.2 – Event-loop correlation and bounded soak projection
Checks
Safety and release
No change to existing 750 ms caller timeout, circuit breaker/backoff, SQL operations, cache semantics, configuration, or DB schema/data. No manual production mutations; standard validated main CI/CD release is the only deployment path. Independent SQL script must be run only by operator with least privilege. Follow with a short, passive 1–2 hour V5 production measurement after deploy and version identity validation.