<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dataframe on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/dataframe/</link>
    <description>Recent content in Dataframe on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/dataframe/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DataFrame Processing Libraries: Polars vs Vaex vs datatable</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-dataframe-processing-libraries-polars-vaex-datatable/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-dataframe-processing-libraries-polars-vaex-datatable/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;When building self-hosted data pipelines, choosing the right DataFrame library can dramatically impact performance, memory usage, and developer productivity. While pandas remains the de facto standard for in-memory data manipulation, three open-source alternatives — &lt;strong&gt;Polars&lt;/strong&gt;, &lt;strong&gt;Vaex&lt;/strong&gt;, and &lt;strong&gt;datatable&lt;/strong&gt; — offer significant advantages for server-side workloads: lazy evaluation, out-of-core processing, and multi-threaded execution.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
