How to read this index
Dated snapshots
Every report is a point-in-time measurement. Quote the report date, workload shape, and runtime assumptions with the number.
Subsystem-specific
PostgreSQL driver, Zig runtime, Qdrant, ORM, and IPC results are tracked separately so one benchmark does not stand in for the whole platform.
Reproducible first
Canonical pages should explain harness, dataset, and reproduction commands before making performance claims.
Current Reports
These are the current benchmark reports to use when evaluating an active subsystem.
qail-zig PostgreSQL driver
qail-qdrant vector driver
qail-pg vs SQLx vs SeaORM
Transport Reports
These reports document cross-language and IPC transport work without conflating them with the core driver pages.
Go IPC vs pgx
Python IPC vs PyO3
Archived Reports
Older reports stay published for context, but they should be read as archive material unless a newer current report does not exist.
Cross-language performance
PostgreSQL Zig 50M query run
ORM/driver benchmark
COPY and query throughput
Pipelining throughput
Reproduce locally
Local reruns matter more than copied headline numbers. Use the repository and harness that matches the report you are reading, then confirm hardware, data, and network assumptions from that report page.
qail.rs workspace
Use the target report page for dataset shape, connection topology, and any required environment variables.
cargo run --example orm_benchmark --releasecargo run --example fair_benchmark --releasecargo run --example batch_benchmark --release
Open repository
qail-zig workspace
The current public Zig benchmark methodology is documented in /zig/docs/benchmarks.html and backed by the qail-zig repository.
zig build ast-benchzig build bench
Open repository