You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Write a blog about parquet predicate pushdown #3464
I think it would be super valuable to write a blog post about all the work from @thinkharderdev@Ted-Jiang, @tustvold and others to make reading from parquet in DataFusion very fast
I have gathered a list of items on #3462 which will perhaps spark some thoughts / ideas.
I made a bit of a start on collecting some data for this. In particular I created something to allow generating parquet files for use in some test benchmarks here.
The basic idea was to show the performance of a selection of relatively simple queries across datafusion-cli and compare it to some other systems like duckdb, trino, polars, spark, etc... Hopefully this would provide ample opportunity to describe the various work that has been performed over the last 9 or so months, and would ground the performance in easily understandable terms.
We could also potentially run benchmarks with various forms of pushdown disabled, to quantify the impact of those changes. Or against older versions of the parquet reader, to quantify the performance impact of things like dictionary preservation
Hopefully this would provide ample opportunity to describe the various work that has been performed over the last 9 or so months, and would ground the performance in easily understandable terms.
Activity
tustvold commentedon Sep 13, 2022
I made a bit of a start on collecting some data for this. In particular I created something to allow generating parquet files for use in some test benchmarks here.
The basic idea was to show the performance of a selection of relatively simple queries across datafusion-cli and compare it to some other systems like duckdb, trino, polars, spark, etc... Hopefully this would provide ample opportunity to describe the various work that has been performed over the last 9 or so months, and would ground the performance in easily understandable terms.
We could also potentially run benchmarks with various forms of pushdown disabled, to quantify the impact of those changes. Or against older versions of the parquet reader, to quantify the performance impact of things like dictionary preservation
alamb commentedon Sep 13, 2022
I agree -- this would be a great start
alamb commentedon Nov 30, 2022
We have a draft of this post ready here apache/arrow-site#280
alamb commentedon Dec 7, 2022
For a variety of reasons we posted this on the Influxdata site first: https://www.influxdata.com/blog/querying-parquet-millisecond-latency/ -- very cool stuff