Repository navigation
bench: record the gateway's Server-Timing with each call - #69
Merged
Merged
Conversation
With tabctx's timings_ms and the gateway's Server-Timing (gateway, upstream; aieng-proxy-gateway#475) on each call, a slow call splits into the client's network, the gateway, the hop to the cluster, and tabctx. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
prod_bench.pynow keeps each response'sServer-Timingheader (gateway,upstream; aieng-proxy-gateway#475) next to tabctx'stimings_ms, in both the slowest-call lists and the--log-callslog. A slow call can then be split into four parts: the client network, the gateway, the hop to the cluster, and tabctx. I ran a smoke test against prod.🤖 Generated with Claude Code