Test Methodology and Interpretation
Every API/database combination was tested independently, with one API and its target database running at a time. Each concurrency level ran for approximately 30 seconds, with an interval between levels and database stabilization before the next group.
Limited database4 CPU8 GB RAM
Full database12 CPU90 GB RAM
The concurrency values represent simultaneous simulated clients. An individual high-throughput measurement is not necessarily the most reliable production choice. Error counts must be considered alongside throughput and latency.
The official raw TSV contains mode, database, language, concurrency, request count, requests/sec, errors and status. Detailed latency measurements remain in the benchmark server's individual run logs, not in this summary file.
No results have been repaired, replaced, or silently excluded for this publication. Zig preflight failures remain explicitly visible; targeted future testing can be published as a separate dated run.