workspaces-performance-system

name

workspaces-performance-system

description

Run and maintain the canonical Workspaces performance contract across debug, installed, release, and CI environments. Use when collecting comparable before/after metrics, asserting scenario budgets, verifying installed-build parity, refreshing baselines, or classifying self-hosted perf lane failures as infrastructure versus product regressions. Prefer this skill over workspaces-optimization when the task is to operate the standardized performance system rather than investigate an unknown slowdown.

Workspaces Performance System

Use this skill when the task is to run the performance system correctly and produce comparable evidence.

Use workspaces-optimization instead when the task is root-cause investigation on a slow machine or an unknown latency path.

Quick Start

Run one canonical debug scenario and assert budgets:

./scripts/perf-runner.sh --scenario debug_no_activate --assert-budget

Compare before and after summaries:

./scripts/perf-compare.py before-summary.json after-summary.json

Verify release-bundle performance signoff on the packaged app:

./scripts/verify-installed-perf.sh build/WorkSpaces.app

Core Workflow

1. Start from the contract

Read these first:

• config/performance/contract.json
• docs/performance/metrics-reference.md
• docs/performance-testing.md

The contract is the source of truth for:

• scenario ids
• metric coverage
• budget formulas
• PR versus scheduled-main gate policy

Do not invent new scenario names or hand-tuned thresholds in ad hoc scripts.

2. Pick the smallest canonical scenario