Comment by srcreigh
3 days ago
The website claims it’s 10x cheaper (“10x faster on same hardware costs”) and implements SQL execution.
I don’t understand why GPU saturation is relevant. If it’s 10x cheaper, it doesn’t matter if you only use 0.1% of the GPU, right?
Correctness shouldn’t be a concern if it implements SQL.
Curious for some more details, maybe there’s something I’m missing.
GPU databases can run a small subset of production workloads in a narrow combination of conditions.
There are plenty of GPU databases out there: mapD/OmniSci/HeavyDB, AresDB, BlazingSQL, Kinetika, BrytlytDB, SQReam, Alenka, ... Some of them are very niche, and the others are not even usable.