Pgbench kernel ab benchmark - #31
Draft
nmanthey wants to merge 1 commit into
Draft
Conversation
nmanthey
force-pushed
the
pgbench-kernel-AB-benchmark
branch
from
August 20, 2026 08:57
ab17330 to
b4be7da
Compare
bhcopeland
marked this pull request as draft
August 26, 2026 09:34
Add a pgbench-kernel-regression VM test that installs a base kernel, runs a PostgreSQL 16 pgbench read-only and read-write suite, reboots into a second (tip) kernel, re-runs the suite, and emits benchmark-base-*.csv and benchmark-tip-*.csv for the regression analyzer to compare (read-only/read-write TPS and average latency). Signed-off-by: Norbert Manthey <nmanthey@amazon.de>
nmanthey
force-pushed
the
pgbench-kernel-AB-benchmark
branch
from
September 2, 2026 14:47
b4be7da to
4d57c0f
Compare
Contributor
Author
|
I rebased the pgbench, and re-executed a c8i.4xlarge × 5 VM run: In case we regress in the future, I'd like to use this test to notify authors/maintainer/... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding the pgbench postgresql benchmark as a new highlevel regression benchmark. Coefficient of variance is low enough to consider this benchmark as a stable benchmark to detect regressions (CV 0.7–1.7%). Since the same postgresql version used. Running multiple test entries in one pipeline works.
Testing Done
Ran the pgbench-kernel-regression test end-to-end on AWS (local-orchestrator path), base kernel 6.1.141-165.249.amzn2023 vs tip 6.1.150-174.273.amzn2023, on c8i.4xlarge in us-west-2 with the al2023-ami-kernel-6.1-x86_64 AMI.
Single-VM run
postgresql.readwrite.latency_avg.
Multi-VM statistical comparison (5 VMs)
Combined config (all touched tests, 2 VMs each)
One config running pgbench-kernel-regression, unixbench-kernel-regression, and simple-unixbench at min_count: 2. 6/6 VMs succeeded. pgbench produced 8 base + 8 tip rows and compared correctly.