Skip to content

chore(spanner): track latency when using KeyAwareChannel#12744

Open
olavloite wants to merge 1 commit intomainfrom
spanner-track-latency
Open

chore(spanner): track latency when using KeyAwareChannel#12744
olavloite wants to merge 1 commit intomainfrom
spanner-track-latency

Conversation

@olavloite
Copy link
Copy Markdown
Contributor

Track latency for streaming SQL and streaming reads that return only one PartialResultSet. The choice for which RPCs are eligible for tracking is done by the LatencyTracker. This allows us to include/exclude more RPCs in the future.

Track latency for streaming SQL and streaming reads that return only one PartialResultSet.
The choice for which RPCs are eligible for tracking is done by the LatencyTracker. This
allows us to include/exclude more RPCs in the future.
@olavloite olavloite requested review from a team as code owners April 10, 2026 13:56
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces latency tracking for Spanner gRPC calls by integrating a LatencyTracker into the ChannelEndpoint and KeyAwareChannel. It specifically measures the time to the first response message for streaming read and SQL operations using an Exponential Weighted Moving Average (EWMA) tracker. Review feedback highlights several breaking changes to the LatencyTracker public API, recommending the use of default interface methods and maintaining the visibility of existing methods to ensure backward compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant