# DuckDB Speed on MySQL with dbtrail, Without a New Storage … | Percona Community

**URL:** <https://forums.percona.com/t/duckdb-speed-on-mysql-with-dbtrail-without-a-new-storage-percona-community/41208>\
**Category:** Community website\
**Created:** [August 26, 2026, 12:03pm UTC](https://forums.percona.com/t/duckdb-speed-on-mysql-with-dbtrail-without-a-new-storage-percona-community/41208 "2026-08-26T12:03:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [August 26, 2026, 12:03pm UTC](https://forums.percona.com/t/duckdb-speed-on-mysql-with-dbtrail-without-a-new-storage-percona-community/41208/1 "2026-08-26T12:03:30Z")

</div>

Two recent posts on the Percona blog caught my attention. In [Replicating from InnoDB into a DuckDB storage engine](https://www.percona.com/blog/replicating-from-innodb-into-a-duckdb-storage-engine/) and [The DuckDB MySQL engine at 500 GB](https://www.percona.com/blog/the-duckdb-mysql-engine-at-500-gb/), Evgeniy Patlan wired DuckDB into mysqld as a storage engine, pointed row-based replication at it, and measured it at TPC-H scale factor 500. The numbers are striking: loads 25 times faster than InnoDB, one fifth of the disk, and the full 22-query TPC-H suite done in 186 seconds where InnoDB needed about 28 hours and never finished four of the queries.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/08/26/duckdb-speed-on-mysql-without-a-new-storage-engine/](https://percona.community/blog/2026/08/26/duckdb-speed-on-mysql-without-a-new-storage-engine/)