NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
Asynchronous I/O in DuckDB: Work, Thread, Work (duckdb.org)
bburnett44 3 hours ago [-]
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?
otterley 3 hours ago [-]
Most cloud providers start with a 2:1 ratio of memory in GiB to CPU cores and go up from there. Databases also are the most common workload for large-memory systems because they benefit so much from large buffer caches.
myshapeprotocol 5 hours ago [-]
Deep dive into asynchronous I/O architectures like this is pure engineering gold for high-performance data processing. Excellent breakdown.
pjot 3 hours ago [-]
I wonder how this would work in trying to parallelize the worker threads (multiple duckdb instances) coordinating them via Quack.

Ducks all the way down!

datadrivenangel 3 hours ago [-]
DuckDB is trending towards becoming a query engine, specifically the fastest analytical query engine. This is very good.
abofh 3 hours ago [-]
Do they have SSL updates yet? Signing is great, but using https means not fighting firewalls to start a job
mansi1010 5 hours ago [-]
This is such a long waited feature!
myshapeprotocol 1 hours ago [-]
Brilliant deep dive into asynchronous I/O and execution thread models. Essential reading for high-performance data engineering.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 07:30:36 GMT+0000 (Coordinated Universal Time) with Vercel.