Skip to content

performance.md

Latest commit

 

History

History
58 lines (44 loc) · 2.59 KB

performance.md

File metadata and controls

58 lines (44 loc) · 2.59 KB
Raw

Desktop performance benchmarks

Rakazo measures the production Vite renderer inside a packaged Electron directory build against a disposable Postgres database, the scripted agent runtime, and the fake sandbox. No provider account or production data is used.

Run a baseline from a local Conductor workspace with Docker available:

pnpm perf:desktop -- --label=before

The command uses CONDUCTOR_PORT and the next allocated port for its web and API servers. Reports are written to .context/performance/<label>.json and .md, which remain local to the workspace. Override the number of cold and warm launch samples when iterating:

pnpm perf:desktop -- --label=quick --samples=2

To compare packaged assets with remote asset loading under a deterministic network delay:

pnpm perf:desktop -- --label=remote-80ms --asset-delay=80 --remote-renderer
pnpm perf:desktop -- --label=bundled-80ms --asset-delay=80 --skip-build

On macOS, compare destroy/recreate against the retained warm window with:

pnpm perf:desktop -- --label=reopen-destroyed --disable-warm-window
pnpm perf:desktop -- --label=reopen-retained --skip-build

After changing one performance-sensitive behavior, record another report and compare them:

pnpm perf:desktop -- --label=after
pnpm perf:compare .context/performance/before.json .context/performance/after.json

Definitions

  • Cache-cold launch uses a fresh copy of an authenticated profile and clears Chromium's HTTP and code caches before navigation. It is not an OS-filesystem cold start.
  • Warm launch fully quits and relaunches Electron while preserving the primed profile and caches.
  • Shell usable means authenticated bots and the active 100-message thread have committed and painted.
  • Settings painted/settled separates React content paint from the end of the panel transition.
  • Typing records keydown to the next animation frame with a 100-message transcript mounted.
  • Idle CPU/memory samples every second for 12 seconds. Summed working-set memory is retained alongside raw per-process samples; Chromium working sets can double-count shared pages.
  • Streaming drives the real subscription/reducer path with scripted progress every 50 ms.

Runtime CPU and launch measurements are informational until enough samples exist on a fixed Mac. Bundle sizes are deterministic enough for automated regression checks. Keep hardware, platform, and build mode fixed. A comparison that intentionally changes Electron or renderer mode measures the combined migration result; it cannot attribute the change to either layer in isolation.