Using 512gb of ram for a 22gb remote file does feel a bit weird for a benchmark but maybe they couldn’t get a large number of cores without lots of memory?

Deep dive into asynchronous I&#x2F;O architectures like this is pure engineering gold for high-performance data processing. Excellent breakdown.

I wonder how this would work in trying to parallelize the worker threads (multiple duckdb instances) coordinating them via Quack.<p>Ducks all the way down!

DuckDB is trending towards becoming a query engine, specifically the fastest analytical query engine. This is very good.

Do they have SSL updates yet? Signing is great, but using https means not fighting firewalls to start a job

Brilliant deep dive into asynchronous I&#x2F;O and execution thread models. Essential reading for high-performance data engineering.

HN

Asynchronous I/O in DuckDB: Work, Thread, Work

Comments (8)