3 Commits

Include renames

Author	SHA1	Message	Date
weichenandCursor	b2e129ab3f	Check host load before creating the pgbench instance ... Why: A timed window that starts under load average above 16 is not a usable baseline, and creating the instance first only to pause wastes a startup. Evidence: The rerun at load 24.03 exited 3 before any timed window and removed the instance. Impact: The pause now happens before initdb. No change to the benchmark itself. Refs: docs/release-multi-instance.md B6 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-12 13:19:40 +00:00
weichenandCursor	5f8de0fc55	Fix pgbench latency samples so summaries exclude the text log ... Why: The percentile reader also opened the pgbench stdout file, so the first run exited 1 after six successful windows. Evidence: Parser check on results/pgbench-20261012-131229 select-only-10 gave p50 0.018 ms, matching the reported average. The timed rerun is recorded next. Impact: Percentile parsing only. The six windows themselves had zero failed transactions. Refs: docs/release-multi-instance.md B6 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-12 13:19:11 +00:00
weichenandCursor	a64afe05e3	Add an isolated pgbench entry for the U7 database baseline ... Why: Checklist B6 needs a repeatable database-only baseline that cannot reach production ports or instances. Evidence: run_pgbench.sh --self-check passed (help, unknown arg, foreign name, busy port, SIGINT cleanup). Timed runs are recorded separately. Impact: New load-test entry and README note. No product or release-gate change. Refs: docs/release-multi-instance.md B6 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-12 13:12:23 +00:00