<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Photon on Dustin Smith's Online Resume</title><link>https://dustinsmith.info/tags/photon/</link><description>Recent content in Photon on Dustin Smith's Online Resume</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 00:19:00 +0700</lastBuildDate><atom:link href="https://dustinsmith.info/tags/photon/index.xml" rel="self" type="application/rss+xml"/><item><title>Databricks Never Skips a Page. Its Writer Does Not Even Write Them</title><link>https://dustinsmith.info/blog/databricks-liquid-clustering/</link><pubDate>Wed, 19 Aug 2026 00:19:00 +0700</pubDate><guid>https://dustinsmith.info/blog/databricks-liquid-clustering/</guid><description>&lt;p&gt;Two posts ago I found that &lt;a href="https://dustinsmith.info/blog/aws-parquet-column-index/"&gt;EMR and Glue never read parquet column
indexes&lt;/a&gt;. Last post I &lt;a href="https://dustinsmith.info/blog/comet-delta-native-scan/"&gt;gave DataFusion Comet
a native Delta read path&lt;/a&gt; so the fastest
reader in that investigation could prune the format I actually run. One
vendor was missing from the scoreboard: Databricks. So I created a
workspace, pointed the same instrumentation at it, and reran the series benchmark
with the platform&amp;rsquo;s own clustering in the ring: classic &lt;code&gt;OPTIMIZE ZORDER BY&lt;/code&gt;
and liquid clustering, against the learned Hilbert curve from the earlier
posts.&lt;/p&gt;</description></item></channel></rss>