Skip to content

Rebuild the site around the benchmark comparison - #78

Open
martian56 wants to merge 1 commit into
quanta-portfrom
site-rebuild
Open

Rebuild the site around the benchmark comparison#78
martian56 wants to merge 1 commit into
quanta-portfrom
site-rebuild

Conversation

@martian56

Copy link
Copy Markdown
Owner

Rebuilds web/ on top of quanta-port, so the site can describe the native
protocol instead of the PostgreSQL wire protocol that branch removes.

What changed

The page opens on the four-engine comparison rather than a claim. The table
sits in the first viewport at full width with its commit, date and container
limits attached, and the workloads QuantaDB loses are drawn at the same
weight as the ones it wins. PostgreSQL's write lead is marked, not buried.

Structure varies section to section instead of repeating one rig: the field
table, the five-machine matrix, a prose pair on the engine, two code blocks,
and the milestone list.

The tables are CI output now

readme_bench.py gained a second target. It rewrites the marked blocks in
web/index.html from the same result artifacts it already uses for the
readme, so the published numbers cannot drift apart, and bench.yml commits
both files. Verified idempotent: running the publisher twice against fixture
data produces identical output.

The five-machine table is now ordered by write throughput, which puts the
Windows runner and its 540 ops/s at the bottom where the callout reads
correctly. A profile is flagged when its writes fall below a quarter of the
best profile's or its write tail passes 20 ms.

Protocol copy

No psql quickstart, no "Speaks PostgreSQL" card, no Postgres wire claim.
The quickstart builds from source, because there is still no published
image, and connects over TCP on 6626.

One thing reviewers should look at

The field numbers were produced by driving QuantaDB through its
PostgreSQL-compatible port with psycopg2, which is what field_bench.py
still does. That port does not exist on this branch. The measurements are
real and the engine path behind them is unchanged, but the comparison is not
reproducible against this commit until reference.yml and field_bench.py
are re-pointed at the native client. The page states this in place rather
than implying the run is current. That harness work is still open.

Supersedes #76.

The page now opens on the four-engine table instead of a claim, with the
commit, date and container limits attached to it, and the workloads QuantaDB
loses shown at the same weight as the ones it wins.

The field and machine tables are written by CI. readme_bench.py rewrites the
marked blocks in web/index.html from the same result artifacts it already
uses for the readme, so the two can never disagree, and the bench workflow
commits both.

Protocol copy now matches the code on this branch: one native protocol on
6626, no psql quickstart, no Postgres wire claim. The field runs predate that
change and say so on the page.

Adds PRODUCT.md and DESIGN.md recording the direction and the rules the build
follows.
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1a98bd27-9f53-42ac-bd2c-f24a774d5ea6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch site-rebuild

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant