perf: record the Woodpecker G4 measured baseline
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
ci/woodpecker/push/main Pipeline was successful
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
ci/woodpecker/push/main Pipeline was successful
The manual .woodpecker/performance.yml workflow ran on the designated fixed agent (platform_id woodpecker-agent-1): 5 warmups + 20 samples, all 9 workloads correctness-verified, CPU 0 pinned from the container cpuset. Two runs differed by -10.9%..+7.1% p50 and -1.9% RSS. The node is a shared Docker container with the powersave governor and loadavg ~5.7-6.1, so the release gate is WARN, not PASS, and comparisons are same-platform only. Store both marqdo.perf.v2 reports and the SHA-bound release manifest. The manifest is DO_NOT_RELEASE only because strict_vm remains UNVERIFIED; Linux, Windows, macOS and performance have real same-SHA results.
This commit is contained in:
1 parent
1199c88e3e
commit
c11c1c858a
7 files changed
+660
-25
No files matched your search
+9
-7
@@ -36,12 +36,14 @@ Rules enforced by the tool:
|
||||
* Development-container smoke run (2026-11-21, `--warmups 1 --samples 3
|
||||
--allow-smoke`): all nine workloads `VERIFIED`/`SMOKE`, no correctness
|
||||
failures. Stored as a smoke artifact, **not** a release baseline.
|
||||
* Remote Woodpecker G4: the repository now has a manual
|
||||
[`.woodpecker/performance.yml`](../.woodpecker/performance.yml) workflow on
|
||||
the designated fixed agent (`platform_id: woodpecker-agent-1`). It runs
|
||||
5 warmups / 20 samples, pins the first CPU in the container's
|
||||
`Cpus_allowed_list`, and records the hardware/toolchain manifest. Trigger it
|
||||
with the Woodpecker API using `"workflow": "performance"`; do not run it on
|
||||
PR code. Its report is the G4 baseline for this node.
|
||||
* Remote Woodpecker G4: **MEASURED provisional baseline** at `1199c88`.
|
||||
The manual [`.woodpecker/performance.yml`](../.woodpecker/performance.yml)
|
||||
workflow ran on the designated fixed agent (`platform_id:
|
||||
woodpecker-agent-1`): 5 warmups / 20 samples, 9/9 correctness verified,
|
||||
pinned CPU 0 from the container cpuset. Two same-day runs differed by
|
||||
-10.9%..+7.1% p50. The agent is a shared Docker container with the
|
||||
`powersave` governor and loadavg ~5.7–6.1, so the gate is **WARN**, not
|
||||
PASS, and comparisons are valid only on this `platform_id`. Evidence:
|
||||
[`evidence/2026-11-21-perf-woodpecker-agent-1.md`](evidence/2026-11-21-perf-woodpecker-agent-1.md).
|
||||
* GitHub G4: `.github/workflows/performance-linux.yml` remains available for a
|
||||
physically separate node.
|
||||
Reference in new issue
Block a user