Measure the complete resource workload.

Count the business outcome

An atomic bundle counts as one business transaction; its resource legs are reported separately. Rejected operations, retries and read traffic must be separated from fresh successful commits.

Batches may improve efficiency, but counting a transport batch or its individual legs as successful business transactions would hide what the system actually accomplished.

A result needs its conditions

Published runs will need the exact source and binary, workload generator, hardware and storage, network topology, replica and quorum settings, payload and bundle sizes, contention, batching, durability settings and run duration.

• Report latency distributions and sustained throughput together.
• Show memory, CPU, storage growth and saturation behavior.
• Include overload, failure, recovery and catch-up workloads.
• Keep correctness checks active and retain reproducible raw results.

Qualification establishes the supported envelope

Benchmarks will establish the supported operating envelope and its limits before performance is marketed. TigerBeetle's published results do not establish Mira's performance: its resource workload and complete implementation need their own measurements.