4 ms·
That's not a great suggestion given the constraints. Kdb costs way more than "a couple hundred per month". Also a billion rows quickly falls outside the 32 bit
by anonu 7y ago
That's not a great suggestion given the constraints. Kdb costs way more than "a couple hundred per month". Also a billion rows quickly falls outside the 32 bit addressable range given most of the calcs happen in memory.
What's wrong with postgresql in this context? OP doesn't mention any speed, latency or bandwidth requirements...
- icsa 7y agoI have built many billion+ row databases on a laptop with 16 GB RAM, using the 32-bit version. kdb+ uses memory mapping and can support databases much larger than available RAM. PostgreSQL is a fine choice and I use it for many projects. However, kdb+ is a much better choice when time-series analysis is required. I'm happy to provide more details if you're interested.