<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vortex on Alfonso Subiotto</title><link>http://asubiotto.com/tags/vortex/</link><description>Recent content in Vortex on Alfonso Subiotto</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 25 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="http://asubiotto.com/tags/vortex/index.xml" rel="self" type="application/rss+xml"/><item><title>Questioning an Interface: From Parquet to Vortex</title><link>http://asubiotto.com/writing/interface-parquet-vortex/</link><pubDate>Tue, 25 Nov 2025 00:00:00 +0000</pubDate><guid>http://asubiotto.com/writing/interface-parquet-vortex/</guid><description>&lt;p&gt;An exploration of how Polar Signals migrated their profiling database from Apache Parquet to Vortex, achieving a 70% average performance improvement across all queries. The shift demonstrates how interface design choices can impose unexpected limitations on system performance.&lt;/p&gt;
&lt;p&gt;Parquet&amp;rsquo;s &amp;ldquo;retrieval&amp;rdquo; differs fundamentally from &amp;ldquo;querying&amp;rdquo;—converting Parquet files to Arrow format for actual computation consumed significant CPU resources. Vortex, with its zero-copy conversion to Arrow and SIMD-friendly encodings, proved to be a better fit for our use case.&lt;/p&gt;</description></item></channel></rss>