<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DuckDB on Percona Community</title><link>https://percona.community/talk_tags/duckdb/</link><description>Recent content in DuckDB 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/duckdb/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><item><title>DuckDB for MySQL Old Timers</title><link>https://percona.community/talks/2026/2026-11-17-duckdb-for-mysql-old-timers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-11-17-duckdb-for-mysql-old-timers/</guid><description>&lt;p&gt;DuckDB is showing up everywhere MySQL people look for analytics. This talk is for old-timers: what DuckDB actually is, how it differs from the InnoDB-shaped mental model, and what to expect when someone embeds a “duck” next to your OLTP data — without pretending it is just another storage engine.&lt;/p&gt;</description></item><item><title>Twenty Years of Bolting Analytics onto MySQL: Will DuckDB Finally Make It HTAP?</title><link>https://percona.community/talks/2026/2026-11-17-twenty-years-of-bolting-analytics-onto-mysql-will-duckdb-finally-make-it-htap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-11-17-twenty-years-of-bolting-analytics-onto-mysql-will-duckdb-finally-make-it-htap/</guid><description>&lt;p&gt;For twenty years we have bolted analytics onto MySQL — slaves, columnar plugins, external warehouses, clever replication tricks. DuckDB changes the toolkit again. Vadim looks at what worked, what did not, and whether DuckDB is finally enough to call the stack HTAP without hand-waving.&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;(Abstract not filed in Jira; short stand-in until the final text lands.)&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>