chat-perf

Detect memory leaks in VS Code chat by running multi-message checks with forced garbage collection to measure heap growth and DOM node retention. This process uses heap snapshots to identify cleanup failures in the streaming and response pipeline.

Benchmark VS Code chat performance by comparing local dev, production, and release builds across chat scenarios using Playwright-driven launches. This spots latency and rendering slowdowns by applying baseline comparisons to the chat UI changes.

Set up CI regression gating for chat UI changes by applying statistically grounded thresholds and baseline comparisons to validate streaming and lifecycle changes in automated pipelines. This produces reliable pass or fail results for chat performance benchmarks.

Yes, chat performance regression testing requires Playwright-driven launches to automate VS Code chat scenarios and capture reliable metrics. Playwright handles the browser automation needed for baseline comparisons and heap snapshots across builds.

You need statistical regression checks for chat performance when validating UI, streaming, and SSE processing changes to avoid false positives. These checks compare current benchmarks against baseline thresholds to produce reliable pass or fail results.