Its sitting at the top in clickbench .Pretty cool https://benchmark.clickhouse.com/#system=-&type=-&machine=-c...
Sirius DB
11–18 of 18 posts
Re: Sirius DB
#12Its sitting at the top in clickbench .Pretty cool https://benchmark.clickhouse.com/#system=-&type=-&machine=-c...
Re: Sirius DB
#13Earlier quoted context omitted.
One downside is that you're paying for the GPU whether you're fully using it or not. It takes big queries to saturate a GH200, and if you're only using 10% of the capacity of the GPU it doesn't really matter that it's 10x faster. In a typical company you'll have jobs, some scheduled, some ad-hoc, at a range of sizes. Most of them won't be cost-effective to run on a GPU instance, so you need a scheduling layer that es…
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.
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.
Re: Sirius DB
#14Its sitting at the top in clickbench .Pretty cool https://benchmark.clickhouse.com/#system=-&type=-&machine=-c...
Re: Sirius DB
#15Re: Sirius DB
#16Re: Sirius DB
#17I wonder if the benefit is primarily for transactional vs analytical queries