Add ScramDB

[vertexclique]

This is a native submission, installed through the official installer pinned to one published build (c664e19).

Results:

• c6a.4xlarge (results/20260905): the reference run, 500 GB gp2.
• c7a.metal-48xl (results/20260906): the same scripts and build, unchanged, 500 GB gp2. On this machine the cold runs and the load are limited by a storage-engine defect on our side, not by the box: the engine keeps only about two I/O requests in flight on EBS, so cold reads and load writes wait on per-request latency (the volume never reached its IOPS or throughput ceiling; CloudWatch queue depth 1.7 to 4.3, burst balance 99 to 100). The hot column is representative of the engine on 192 vCPU; the cold and load columns will improve when the queue-depth fix ships, and the result will be re-run then.

[github-actions]

Results for scramdb are ready for: c6a.4xlarge.
The result files are committed as 24721c9.
Removed manually added result files: scramdb/results/20260905/c6a.4xlarge.json, scramdb/results/20260906/c7a.metal-48xl.json.

Logs:

• scramdb on c6a.4xlarge: benchmark log, cloud-init log

[github-actions]

Results for scramdb are ready for: c6a.4xlarge, c6a.metal, c7a.metal-48xl, c8g.4xlarge, c8g.metal-48xl.
The result files are committed as 0dbbedd.

Logs:

• scramdb on c8g.4xlarge: benchmark log, cloud-init log
• scramdb on c6a.4xlarge: benchmark log, cloud-init log
• scramdb on c8g.metal-48xl: benchmark log, cloud-init log
• scramdb on c7a.metal-48xl: benchmark log, cloud-init log
• scramdb on c6a.metal: benchmark log, cloud-init log

[github-actions]

Results for scramdb are ready for: c6a.2xlarge.
The result files are committed as 6a6ef4e.

Logs:

• scramdb on c6a.2xlarge: benchmark log, cloud-init log

[github-actions]

Results for scramdb are ready for: c6a.xlarge.
The result files are committed as 8785040.

Logs:

• scramdb on c6a.xlarge: benchmark log, cloud-init log

[github-actions]

Results for scramdb are ready for: c6a.large.
The result files are committed as d5586ef.

Logs:

• scramdb on c6a.large: benchmark log, cloud-init log

[github-actions]

The run of scramdb on t3a.small did not produce results.

Logs:

• scramdb on t3a.small: benchmark log, cloud-init log