Add Time-to-Render Performance Tracking for Rovo Dev Chat Responses #1400
+54
−3
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.
What Is This Change?
Overview
This PR adds performance telemetry to track the complete end-to-end latency of Rovo Dev chat responses, specifically measuring the time from when the last message is received (from API or replay) until it’s fully rendered in the UI.
How It Works
Added timeToRender event to RovoDevPerfEvents for tracking UI render performance
2. Render Time Measurement Flow
The measurement captures the time between when messages are sent to the webview and when React completes rendering them:
Last Message Received → Store Timestamp → Send to UI → React Renders → Signal Complete → Calculate & Log