TigerBench
No file loaded.
Heads up! This is Python performance. Imagine the speed boost from an implementation in Go 🐹 or Zig ⚡️.
PG Only: PostgreSQL for Orders, Accounting (Tickets), and PaymentSessions.
PG Redis: PostgreSQL for Orders and Accounting (Tickets), and Redis for PaymentSessions.
TB Redis: PostgreSQL for Orders, TigerBeetle for Accounting (Tickets), and Redis for PaymentSessions.

Operations Explained

The Reserve and Commit phases are focused benchmarks designed to measure the theoretical maximum throughput of our API when handling direct accounting operations.

Reserve: The initial accounting operation to provisionally secure a "ticket" resource.

Commit: The final accounting operation to permanently issue a "ticket" resource.

Checkout: Simulates the complete user-facing process of reserving a ticket before payment.

Webhook: Simulates the backend processing that occurs after a successful payment confirmation.

↑ HIGHER = BETTER

Reserve — ops/s

Commit — ops/s

Reserve — ops/s vs concurrency

Commit — ops/s vs concurrency

Checkout — ops/s

Webhook — ops/s

Checkout — ops/s vs concurrency

Webhook — ops/s vs concurrency