Skip to content

Recalibrate Windows warm P50 budget for schema-v2 variance #513

Description

Problem

PR #512 changes only warm P95 budgets, but its first Windows performance job failed the unchanged warm full-refresh P50 gate:

  • exact schema-v2 baseline ad7ca14: 105ms
  • schema-v2 PR measurements for unchanged product code: 117ms, 133ms, 160ms, 164ms, and 182ms
  • existing budget: 50ms / 30%, which blocks above 155ms for that baseline

Three observed PR runs therefore exceed the effective ceiling produced by the unusually low merged baseline, despite stable warm P95, cold P50, inventory, and timeout diagnostics. The isolated #512 rerun passed at 117ms, confirming runner variance rather than a product change.

Scope

After #512 merges:

  • calibrate the Windows warm full-refresh P50 dual budget from repeated schema-v2 hosted runs;
  • keep Linux/macOS P50, all P95, cold-refresh, startup, coverage, and schema behavior unchanged unless independent evidence requires otherwise;
  • add tests proving observed Windows variance passes and a material median regression fails;
  • update docs/QUALITY_SNAPSHOTS.md with the calibration source.

Acceptance criteria

  • repeated unchanged-head Windows schema-v2 runs stay green;
  • a sustained Windows warm median regression fails a tested gate;
  • Linux/macOS and cold/tail gates are unchanged;
  • full CI, coverage, performance, CodeQL, and comparator tests pass.

Depends on #512.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestimportantIssue identified as high-priority

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions