4 ms·
DuckDB is awesome. As a comparison, I have a dataset that starts life as a 35gb set of json files. Imported into Postgres it's ~6gb, and a key query I run takes
by samwillis 4y ago
DuckDB is awesome. As a comparison, I have a dataset that starts life as a 35gb set of json files. Imported into Postgres it's ~6gb, and a key query I run takes 3 min 33 seconds.
Imported into DuckDB (still about ~6gb for all columns), the same SQL query takes 1.1 second!
The key thing is that the columns (for all rows) the query scans total only about 100mb, so DuckDB has a lot less to scan. But on top of that it's vectorised query execution is incredibly quick.
https://mobile.twitter.com/samwillis/status/1633213350002798593 https://mobile.twitter.com/samwillis/status/1633213350002798...
- pletnes 4y agoI found that exporting big tables as a bunch of parquet files is faster and uses less memory than duckdb’s internal format.
- samus 4y agoPostgreSQL would probably be way faster if you add proper indexes.
- mattpallissard 4y agoAnd not store the data as Json/jsonb to begin with.