Performance and throughput
Off-chain execution, order throughput and performance measurement.
Chain finality is outside the order path
The hybrid design separates the fast trading path from blockchain settlement. Eligible orders pass risk checks, match and reach durable commitment off-chain. The resulting obligations are netted and submitted to Canton asynchronously. The trading response does not wait for a Canton settlement confirmation.
Keeping that blockchain round trip out of the order path supports low-latency execution and high order throughput. Off-chain risk checks, replication and durability still govern when a committed outcome can be released. Measured capacity depends on the workload and completion boundary defined below.
Orders, fills and settlement
Execution and settlement measurement
Drag to pan, or use arrow keys when the diagram is focused. Use plus and minus to zoom, and zero to fit. On a touch screen, pinch to zoom.
Throughput is measured at distinct stages of the trading lifecycle. An order can rest, be rejected, be cancelled or produce multiple fills. Execution outcomes become committed off-chain; netting then combines obligations for asynchronous Canton settlement.
Order rate, committed execution rate and Canton settlement rate therefore use different units and completion boundaries. Record each separately when evaluating performance.
Off-chain throughput target
Edel Markets targets approximately 140,000 orders per second on the off-chain execution path. Matching, risk and order commitment operate independently of Canton settlement, so blockchain confirmation is outside the order response.
This is an engineering target. Sustained committed throughput depends on workload, replication and deployment configuration; it is separate from Canton transaction throughput and is not a production service guarantee.
Performance measurement
We evaluate throughput at a defined completion point: order acceptance, replicated COMMITTED or Canton settlement. A reproducible measurement also specifies the build, environment, order mix, distribution across markets and accounts, concurrency and run duration.
Successful and rejected outcomes, tail latency and recovery behavior provide context for the throughput figure. Incoming request rate and queue capacity are separate measurements; they do not establish how much work completed. See integration testing for checks you can apply to your own client.