I see you are running eager polars. E.g. using read_parquet. To do a fair comparison you must scan_parquet, write your query lazily and collect at the end.
Now duckdb can use query optimization, whilst polars cannot because you force every operation to execute immediately. That's not an apples vs apples comparison.
I see you are running eager polars. E.g. using
read_parquet
. To do a fair comparison you mustscan_parquet
, write your query lazily and collect at the end.Now duckdb can use query optimization, whilst polars cannot because you force every operation to execute immediately. That's not an apples vs apples comparison.