Transaction Throughput Calculator

Work out transaction throughput instantly with clear inputs, formula shown and shareable results.

About Transaction Throughput Calculator

Transaction throughput is concurrency divided by transaction duration, where duration is the statement work plus one durable commit. Commit latency is the fsync to the write-ahead log, and it dominates when transactions are small: a 1.2 ms fsync on a transaction doing 3.6 ms of work is a quarter of the total, which is why group commit and battery-backed write caches matter so much.

Formula

Transaction throughput

transaction time = commit latency + statements x statement time; TPS = concurrent sessions x 1000 / transaction time

Worked example

With the default values below, Transaction Throughput Calculator returns Transaction throughput of 6,667. Change any input above and every figure here is recalculated in your browser.

Inputs used

Commit latency (fsync)minimum 0.001 ms: 1.2 ms
Concurrent writing sessionsminimum 1: 32
Statements per transactionminimum 1: 6
Time per statementminimum 0.001 ms: 0.6 ms

Results

Transaction throughput: 6,667 tps
Transaction latency: 4.800 ms
Share of transaction time spent committing: 25.0%
Statement rate: 40,000

Step by step

1Values used
2Transaction throughput
3Transaction throughput= 6,667 tps
4Transaction latency= 4.800 ms
5Share of transaction time spent committing= 25.0
6Statement rate= 40,000

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to 3 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

What is group commit?

The engine batches several transactions' log flushes into one fsync, so per-transaction commit cost falls as concurrency rises. It is why throughput can scale better than the single-transaction latency suggests.

Is disabling synchronous commit safe?

It multiplies throughput but risks losing recently committed transactions on a crash. Acceptable for derived or replayable data, not for financial records.