Performance & Benchmarking

Performance tuning and benchmarking for MariaDB Exa: the MaxScale CDC (binlogrouter) odbc_perf_* bulk-load parameters, plus CDC throughput up to 600 TPS and TPC-H benchmark results.

Performance Considerations

MariaDB Exa keeps Exasol in sync through MaxScale CDC, which reads the MariaDB binary log with the binlogrouter module and bulk-loads batches into Exasol over the Exasol ODBC driver. The bulk-load pipeline's throughput is controlled by the odbc_perf_* parameters on the binlogrouter CDC service. The defaults suit most workloads; raise the batch size for more throughput, or lower odbc_perf_ncycles if memory use is high.

Component	Key parameter	Default	Description & tuning tips
MaxScale CDC	odbc_perf_batch_size	200 MB	Size in bytes of one ODBC batch over the wire. Raise for more throughput.
MaxScale CDC	odbc_perf_max_buffered_rows	750,000	Ceiling of buffered rows before a batch is sent.
MaxScale CDC	odbc_perf_max_idle_rows	400,000	Rows buffered before sending when the pipeline is otherwise idle.
MaxScale CDC	odbc_perf_ncycles	4	Maximum parallel ODBC cycles (also the maximum value). Lower it if memory use is high.
MaxScale CDC	odbc_perf_nthreads	0 (unlimited)	Maximum threads used in ODBC processing.
Exasol	NUM_NODES, DB_RAM_SIZE	—	Scale based on dataset size and concurrency.
Network	10 Gbps+ recommended	—	Ensures low-latency data transfer between MaxScale and Exasol.

These parameters are set on the binlogrouter CDC service. For the full CDC setup, see the MariaDB MaxScale Exasolrouter Tutorial.

Benchmarking

MariaDB Exa CDC has been tested and is expected to work in near real-time up to 600 TPS from the source MariaDB server side. MariaDB Exa has leading benchmark results for TPC-H.

_{This page is: Copyright © 2026 MariaDB. All rights reserved.}