Perf VM and bench runner for performance gates #4

New issue

Open

opened 2026-10-05 14:17:09 +00:00 by kayg · 0 comments

kayg commented

2026-10-05 14:17:09 +00:00

Owner

Benchmarks need a quiet, pinned machine. A shared box gives noisy results, and teams start to ignore noisy gates. Decisions 41 and 42.

Choose the host: there is already a NetBird peer perf-test-69-63 (10.69.69.63). Find out if it can be reused.
Dedicated, pinned cores and no other workloads
A Forgejo runner with label perf for scripts/verify bench
Baseline A/B against the base commit, with results in the PR

Benchmarks need a quiet, pinned machine. A shared box gives noisy results, and teams start to ignore noisy gates. Decisions 41 and 42. - [ ] Choose the host: there is already a NetBird peer `perf-test-69-63` (10.69.69.63). Find out if it can be reused. - [ ] Dedicated, pinned cores and no other workloads - [ ] A Forgejo runner with label `perf` for `scripts/verify bench` - [ ] Baseline A/B against the base commit, with results in the PR

kayg referenced this issue

2026-10-06 11:43:21 +00:00

S1: foundations + SSH plugin #9

kayg referenced this issue from a commit

2026-10-06 14:06:30 +00:00

Add perf-run, the shared benchmark lock for the perf VM

kayg referenced this issue from a commit

2026-10-06 14:07:07 +00:00

perf-run: also wait on calternal's legacy lock until it becomes a symlink

~~kayg referenced this issue 2026-10-28 17:53:56 +00:00~~

Orchestrator handover 2026-10-28: moving to a new machine #254

kayg referenced this issue