<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/c01032e2e58b40a19394404b8f78d5a8&quot; frameborder=&quot;0&quot; width=&quot;1720&quot; height=&quot;1290&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1290</height><width>1720</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1290</thumbnail_height><thumbnail_width>1720</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c01032e2e58b40a19394404b8f78d5a8-fbb88442e6037d41.gif</thumbnail_url><duration>166.272</duration><title>ClickHouse tuning, live — same query, 1.8 GB → 6 MB scanned (runnable + CI-verified)</title><description>A 3-minute runnable proof for the ClickHouse role. Same 50M-row events table in two schemas — naïve vs tuned. Both return the same answer, but the naïve one scans 50M rows / 1.8 GB while the tuned one reads 478K / 6 MB — ~280× less data, from ORDER BY + partitioning + a projection. Runs from one command (Docker only, synthetic data, no credentials), and a GitHub Actions job re-runs the benchmark on every push and fails if the tuning regresses.
 Repo: github.com/boheastill/clickhouse-dwh-tuning-demo3</description></oembed>