Evaluating Performance Improvements in MariaDB 10.5.5

August 14, 2020
Author
Vadim Tkachenko
Share this Post:

MariaDB no longer meeting your needs?

Migrate to Percona software for MySQL – an open source, production-ready, and enterprise-grade MySQL alternative.

Learn More

Performance Improvements in MariaDB 10.5.5
Recently, I published a series of posts on MySQL and MariaDB where MariaDB 10.5.4 did not perform well in some scenarios:

In comments on the NVMe post, it was noted that MariaDB 10.5.4 had known performance bugs that would be fixed in MariaDB 10.5.5. Now that MariaDB 10.5.5 is available, it includes:

  • Fixes to performance regressions introduced in 10.5.4
  • General performance improvements across multiple areas

This post revisits those benchmarks using MariaDB 10.5.5.

All tests use sysbench-tpcc (1000 warehouses, ~100GB dataset) under the following scenarios:

  • SATA SSD, innodb_buffer_pool_size=140GB (CPU-bound)
  • NVMe, innodb_buffer_pool_size=140GB (CPU-bound)
  • SATA SSD, innodb_buffer_pool_size=25GB (IO-bound)
  • NVMe, innodb_buffer_pool_size=25GB (IO-bound)

SATA SSD, 140GB Buffer Pool (CPU-bound)

MariaDB comparison

After warm-up differences, performance is roughly the same between versions.

comparison 2500 sec

SATA SSD, 25GB Buffer Pool (IO-bound)

This scenario shows improvements in MariaDB 10.5.5:

improvements

MariaDB 10.5.5 improves throughput and even exceeds MySQL 8.0.21 on average, though with higher variability.

NVMe, 140GB Buffer Pool (CPU-bound)

Performance is similar to 10.5.4, with slightly worse results and an initial drop before recovery.

NVMe, 25GB Buffer Pool (IO-bound)

This scenario exposes a severe issue in MariaDB 10.5.5 (MDEV-23399).

Throughput frequently drops below 100 TPS, compared to over 5000 TPS in MySQL.

Conclusion

MariaDB 10.5.5 introduces improvements in some IO-bound scenarios, particularly on SATA SSD.

However, performance on NVMe under IO-bound workloads is significantly degraded due to a critical bug.

This makes MariaDB 10.5.5 unsuitable for certain production workloads until the issue is resolved.

0 0 votes
Article Rating
Subscribe
Notify of
guest

0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

Far
Enough.

Said no pioneer ever.
MySQL, PostgreSQL, InnoDB, MariaDB, MongoDB and Kubernetes are trademarks for their respective owners.
© 2026 Percona All Rights Reserved