3 ms·
It's about "how fast DuckDB can run the 1.1 billion taxi rides benchmark", with the bulk of the article dedicated to importing the data. It's not about use in p
by tgv 3y ago
It's about "how fast DuckDB can run the 1.1 billion taxi rides benchmark", with the bulk of the article dedicated to importing the data. It's not about use in production for schedule 1B rides or storing the records associated with these rides.
- dang 3y agoOk, we've stuffed a 'benchmark' in the title above.
- kermatt 3y agoThat is in part because DuckDB would not be used in an application supporting multiple concurrent clients. It’s a desktop / single process analysis tool, not a replacement for what a ride sharing app would use for ride scheduling.