Urgent.News

600+ sources. One page. See who else covered it.

Editions

Tech

Twenty-Five Million Rows in Five Seconds, and How to Check

Benchmarks in this industry are mostly untrustworthy, and usually for the same reason: the person running them chose the shape of the work. So let us be precise about what this is and what it is not. This is not a comparison against dbt. dbt is not an execution engine — it generates SQL and hands it to your warehouse — so "Interlace versus dbt" would be measuring DuckDB against whatever you…

This benchmark demonstrates the capabilities of the Interlace tool for processing large datasets in real-time. The test involved generating 25 million synthetic events and processing them through a complex data flow using six different strategies. The work was executed on a machine with AMD Ryzen 9 9955HX3D processor, 16 cores, 32 threads, and 60 GB of RAM.

The results showed that the entire process completed in 5.11 seconds, with the CPU usage reaching 270% at peak. The memory usage remained under 2 GB throughout the process, thanks to the use of streamed Arrow RecordBatches instead of materializing data into pandas. This shows that the same task can be accomplished in just a few seconds on standard hardware, making it an accessible and efficient solution for real-time data processing.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Five things that break when you move from Jest to Vitest

Vitest advertises a Jest-compatible API, and it delivers. describe , test , expect , toHaveBeenCalledWith — all identical.

  • Vitest's global scope differs from Jest's, requiring explicit opt-in through globals in config file.
  • Vitest's jest.mock hoisting behavior requires using vi.hoisted instead of Jest's jest.mock.

More from Saturday 15 August →