# Transaction benchmark methodology

Define transaction throughput, correctness and durability before comparing database performance.

Source: https://particledb.ai/benchmarks/tpc-c/

A transaction benchmark needs a declared workload, successful transaction count and persistence policy. A throughput number alone does not establish application suitability.

## Report the workload

Include transaction definitions and mix, scale, clients, concurrency, run duration, ramp-up and warmup. Count committed transactions separately from attempted or failed transactions.

## Preserve correctness

Check application invariants and result correctness before interpreting throughput. Record transaction isolation, retry policy and every persistence setting. A configuration that skips durable logging is not a durable-commit comparison.

## Naming

A workload inspired by TPC-C is not automatically an audited TPC-C result. Avoid implying certification or comparability unless the required specification and disclosures are satisfied.

## Reproduction

If the exact driver or workload is unavailable, the number cannot be independently reproduced. Do not use that result as a current homepage comparison.

[Shared methodology](/benchmarks/overview/)
