Skip to content

perf: add first-turn timing diagnostics for new-tab sessions - #53

Merged
luoxuanzao merged 1 commit into
mainfrom
perf/first-turn-timing-diagnostics
Sep 1, 2026
Merged

perf: add first-turn timing diagnostics for new-tab sessions#53
luoxuanzao merged 1 commit into
mainfrom
perf/first-turn-timing-diagnostics

Conversation

@luoxuanzao

Copy link
Copy Markdown
Member

Summary

  • Adds [qoderian perf] timing logs across the new-tab → first-session chain so slow first replies can be attributed to a concrete stage instead of guesswork.
  • Instrumented stages: tab.create / tab.restore / tab.switchTo, turn.buildSubmission / turn.titleGeneration / turn.serviceInit / turn.prepareTurn, runtime.spawnPersistentQuery, runtime.cliFirstMessage (CLI cold-start), runtime.applyDynamicUpdates, turn.enqueueToFirstChunk, plus end-to-end turn.firstChunk / turn.total and the background title.coldStartQuery.
  • Pure instrumentation — no behavior changes. Labels are fixed stage names without user data, so logs are safe to paste into bug reports.

Verification

  • npm run typecheck
  • npm run lint
  • npm run test (3481 tests)
  • npm run build
  • npm run release:check
  • npm run audit:prod (0 vulnerabilities)
  • Tested affected qodercli behavior against a real CLI when applicable (n/a — instrumentation only; SDK mock covers the message flow)

Safety

  • No credentials, private vault content, internal URLs, or personal paths are included
  • User-visible changes are documented in CHANGELOG.md

Instrument the new-tab first-session chain with [qoderian perf]
logs so latency regressions can be attributed to a concrete stage:
tab create/switch, turn build/title-gen/service-init/prepare,
persistent-query spawn, CLI cold-start to first message, enqueue to
first chunk, and end-to-end first-chunk/turn totals.
@luoxuanzao
luoxuanzao merged commit 9687fcf into main Sep 1, 2026
10 checks passed
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