Skip to content

chore: establish and document performance baseline (pre-modification) #6

Description

@digital-michael

Goal

Measure and record input-handling performance on the unmodified fork before any SeamGate changes. This baseline is required by the Project Charter (§15) and must be captured before code changes begin.

Metrics to capture (per §15)

  • End-to-end keystroke latency (p50/p95/p99) — local loopback
  • Mouse cursor latency (p50/p95/p99)
  • CPU utilisation (server + client, idle and under load)
  • Memory footprint (server + client, steady state)
  • Reconnect time after network drop

Acceptance criteria

Notes

Every subsequent phase gate requires a performance report showing no regression vs this baseline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase:0Phase 0 — Fork, rename, CI, toolingtype:choreMaintenance, tooling, CI, build

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions