Skip to content

Add PostgreSQL result for c6a.2xlarge (2026-09-18) - #2086

Open
KazukiKandaKK wants to merge 3 commits into
ClickHouse:mainfrom
KazukiKandaKK:add-postgresql-c6a2xlarge-20260918
Open

KazukiKandaKK wants to merge 3 commits into
ClickHouse:mainfrom
KazukiKandaKK:add-postgresql-c6a2xlarge-20260918

Conversation

@KazukiKandaKK

Copy link
Copy Markdown
Contributor

Adds a PostgreSQL 17.11 result on c6a.2xlarge (8 vCPU / 16 GiB, gp3 220GB). Ran the usual benchmark.sh path (43 queries × 3 runs, plus the concurrent QPS follow-up). Existing PostgreSQL results are from 2022/2025 on c6a.4xlarge only; this is a smaller machine.

  • Load time: 1835.506s (99,997,497 rows)
  • Data size: 95,232,178,618 bytes
  • Query 10, run 3 failed (null); left as null
  • The table is 68 GiB on disk and does not fit in 16 GiB RAM, so most queries here are limited by disk I/O, not query complexity.

Sorry the MonetDB result in #2082 is still unresolved on my end. I posted a working theory for the CI failure there and will follow up separately. Didn't want that to block this PostgreSQL submission.

Existing PostgreSQL results were from 2022/2025 on c6a.4xlarge only.
This adds a fresh run on c6a.2xlarge (8 vCPU / 16 GiB, gp3 220GB)
using PostgreSQL 17.11 via the official APT repository, following
the standard benchmark.sh flow (43 queries, 3 runs each, plus the
concurrent QPS follow-up).

- Load time: 1835.506s (99,997,497 rows)
- Data size: 95,232,178,618 bytes
- Query 10, run 3 failed (null) - recorded as-is per the result format

Note: the table (68 GiB on disk) does not fit in this instance's
16 GiB RAM, so most queries are dominated by disk I/O throughput
on this hardware rather than query complexity. Numbers are reported
as measured.
@alexey-milovidov alexey-milovidov added the machine:all PR benchmark on every machine type label Sep 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Results for postgresql are ready for: c6a.metal, c7a.metal-48xl, c8g.metal-48xl.
The result files are committed as fc0db92.
Removed manually added result files: postgresql/results/20260918/c6a.2xlarge.json.

Logs:

@github-actions

Copy link
Copy Markdown
Contributor

The run of postgresql on c6a.2xlarge did not produce results.
The run of postgresql on c6a.4xlarge did not produce results.
The run of postgresql on c6a.large did not produce results.
The run of postgresql on c6a.xlarge did not produce results.
The run of postgresql on c8g.4xlarge did not produce results.
The run of postgresql on t3a.small did not produce results.

Logs:

@github-actions

Copy link
Copy Markdown
Contributor

Results for postgresql are ready for: c6a.2xlarge.
The result files are committed as 0eaa832.

Logs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

machine:all PR benchmark on every machine type

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants