<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Benchmark on Percona Community</title><link>https://percona.community/talk_tags/benchmark/</link><description>Recent content in Benchmark on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><atom:link href="https://percona.community/talk_tags/benchmark/index.xml" rel="self" type="application/rss+xml"/><item><title>Duck Hunt: An Independent Benchmark of DuckDB-Powered MySQL</title><link>https://percona.community/talks/2026/2026-11-17-duck-hunt-an-independent-benchmark-of-duckdb-powered-mysql/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-11-17-duck-hunt-an-independent-benchmark-of-duckdb-powered-mysql/</guid><description>&lt;p&gt;Everybody&amp;rsquo;s putting a &amp;ldquo;Duck&amp;rdquo; in their database: AliSQL, MariaDB, VillageSQL, Percona, Postgres. The promise is fast analytics on your OLTP data. So we went hunting.&lt;/p&gt;&#10;&lt;p&gt;Every engine ran the same TPC-H workload on the same hardware, against InnoDB, PostgreSQL and plain DuckDB. A timing only counted once its answer was checked. The speedups are real, but there might be a few unexpected surprises.&lt;/p&gt;&#10;&lt;p&gt;Come find out what these ducks are good at and where they bite!&lt;/p&gt;</description></item></channel></rss>