3 ms·
You know what? It's even worse. They took /my/ article, refashioned it, and inserted themselves in! https://hackernoon.com/which-gpu-database-is-right-for-me-
by arnon 9y ago
You know what? It's even worse.
They took /my/ article, refashioned it, and inserted themselves in!
https://hackernoon.com/which-gpu-database-is-right-for-me-6ceef6a17505 https://hackernoon.com/which-gpu-database-is-right-for-me-6c...
Also, they flat out don't understand MapD, Kinetica or SQream if they say Kinetica and SQream DB don't support nested queries (because they do).
- pgv 9y agoNested queries are great but I am far more interested in the other features mentioned. I could be wrong but I as far as I am aware MapD, Kinetica and SQream don't have all of these covered?
- arnon 9y agoSome do, some don't. It's not as simplistic as that. Saying "Do you need a large amount of Data?" and then saying not to use GPU databases ignores SQream's experience in managing more than 1PB of data, and Kinetica's experience in clustering multi-TB machines.
- pgv 9y agoI thought the flow diagram was promoting the use of GPUs for large datasets... Brytlyt is a GPU database right?