Polars 2.0
- ID
- 32612
- Status
- summarized
- Published
- 06 Oct 2026, 7:59 PM
- Fetched
- 07 Oct 2026, 10:10 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://pola.rs/posts/release-polars-2/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 07 Oct 2026, 10:11 AM
- Tags
- Audience
- developersdatabase_learnersai_ml_learners
What happened
Polars 2.0 shipped on 6 Oct 2026, with the release post by Ritchie Vink covering initial out-of-core (spill-to-disk) support, a new Map dtype, stricter dtype handling and explicitness, and SQL promoted to a first-class interface. The post reports first-party TPC-H/TPC-DS benchmarks on a c7a.4xlarge (16 vCPU, 32 GB) and a c7a.metal (192 vCPU, 384 GB) against DuckDB 1.5.6, DuckDB 2.0 alpha (2.0.0.dev2610011535) and DataFusion 54.0.0, best-of-5 runs with a 60-second timeout, claiming Polars is fastest on all but one benchmark. DataFusion timed out on TPC-DS q72 (and once on q67) and ran out of memory on TPC-H q18 on the smaller machine, and those queries are excluded from the comparison for all engines. The Hacker News thread drew 416 points and 96 comments.
Why it matters
If you have a pandas or DuckDB job that dies on a laptop with 16 GB of RAM, Polars 2.0's spill-to-disk support is the specific new thing worth testing this week, and SQL as a first-class interface means you can reuse existing SQL rather than rewriting in the expression API. Read the benchmark numbers with care before switching: they are first-party, and the queries where DataFusion failed (q72, q67, q18) were dropped from the sums and geometric means for every engine, so the headline win excludes the cases that were hardest for a competitor. The reported constant overhead when scaling to 192 threads is also the number to watch if you run Polars on large multi-core cloud instances rather than a laptop.
Discussion angle
Run one of your own slowest dataframe or SQL queries on Polars 2.0, DuckDB 1.5.6 and DataFusion on your own hardware before trusting the release-post charts — and ask whether excluding DataFusion's failed queries (q72, q67, q18) is a fair comparison or one that flatters the winner.