bench: asyncpg vs TurboAPI+pg.zig Docker benchmarks#56
Merged
Conversation
Fully reproducible: cd benchmarks/postgres && docker compose up --build Each test runs in its own subprocess (no resource contention). Tests: asyncpg concurrent, Turbo cached, Turbo no-cache (varying IDs via lua), Turbo raw SQL (random + ILIKE). Results (Postgres 18, Docker, sequential, aarch64): Cached by-ID: 18.4x vs asyncpg (361k vs 19k) No-cache by-ID: 4.3x vs asyncpg (83k vs 19k) Cached list: 21.3x vs asyncpg (391k vs 18k) No-cache list: 19.2x vs asyncpg (353k vs 18k) Raw ILIKE: 28.7x vs asyncpg (350k vs 12k) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Results
Reproduce
cd benchmarks/postgres docker compose up --buildTest plan