When building an application on top of Formance Ledger that is set out for scale, it is important to understand the performance characteristics of the ledger. This document summarizes the cost model for each type of ledger operation.

​
Costs breakdown

Request pattern (Ledger v1)Complexity model
Transaction commitO(N) + W
Aggregation • balancesO(Log(N)*M)
Point query • accountsO(1)
Range query • accountsO(Log(N))
Point query • transactionsO(1)
Range query • transactionsO(Log(N))
The complexity model is based on the in-process cost, and doesn’t take into account the networking cost.

​
Data volume

In the architecting for scale section, we outline different strategies to handle a growing volume of ledger data, with a focus on efficient usage of multiple ledgers.

​
Benchmarking

Formance Ledger releases are tested against our load testing suite. The suite can be run locally by following the instruction in the repository. Should you venture out common patterns and ledger architectures, you can customize the suite to have it fit the best your use case and bring the ledger into the least favorable cost-wise conditions.