News for hackers. Stuff that matters.
Re:SQL on Distributed GPUs now available on AWS Marketplace by qeternity on Wednesday March 29, 2017 @02:29PM (#13989179)
This just seems like something riding GPU hype. We run a medium sized Memsql cluster, and get better performance on larger tables with more complex joins than they do in their demo video...and we do this for much cheaper than the lowest g2 instance + AMI. Our data is quite narrow, so fits in RAM quite well, but I would bet that even Citus would fare quite well against this.
Re:SQL on Distributed GPUs now available on AWS Marketplace by felipe_aramburu on Wednesday March 29, 2017 @05:17PM (#13990650)
If your problem can fit in RAM then this is probably not something that would help you. This solution is for people who are looking for massive scale. Also you are running a query from memory. We can run from memory as well and get much better throughput. The new version of BlazingDB also incorporates skip data which can improve join performance by several orders of magnitude for complex joins.
Re:SQL on Distributed GPUs now available on AWS Marketplace by qeternity on Wednesday March 29, 2017 @05:38PM (#13990841)
What are you talking about? I am talking about terabytes of RAM in the cluster. I would love to see some benchmarks of terabyte datasets. Everything I saw from your demo video was under 1b rows. Hardly qualifies as massive scale.
Re:SQL on Distributed GPUs now available on AWS Marketplace by felipe_aramburu on Wednesday March 29, 2017 @05:53PM (#13990956)
When we think about TB of data we do not want to store that in RAM. So if you are looking at a 10TB dataset. You may be willing to have 10TB of ram to fit it in but we aren't trying to solve that problem. We try to solve the problem of reducing the amount of information that has to be pulled from disk to be analyzed by having fine grain partitioning and using data skipping. We are optimizing the compression and decompression of the data to reduce file i/o bottleknecks. So your 10TB dataset can be analyzed with a 100GB of RAM. I agree that video is not very compelling. We are giving a talk at GTC that will show you something 3 orders of magnitude more interesting than that. https://gputechconf2017.smarteventscloud.com/connect/search....
Re:SQL on Distributed GPUs now available on AWS Marketplace by ruw1090 on Wednesday March 29, 2017 @09:46PM (#13992244)
So blazing db mainly uses gpus to speed up compression/decompression? How do gpus help with partitioning and data skipping?
Re:SQL on Distributed GPUs now available on AWS Marketplace by felipe_aramburu on Wednesday March 29, 2017 @10:11PM (#13992328)
BlazingDB uses gpus to speed up transformations, predicates, running predicates on skip data metadata, gpu accelerated join algorithms. In terms of partitioning we use both to generate the data skipping meta data on the partitions and to reorder data around so that we can minimize the number of comparisons joins will likely require or reduce the number of partitions that need to be operated on. At large scale reorganizing information becomes very expensive the gpus allow us to crunch those numbers very quickly.
Re:SQL on Distributed GPUs now available on AWS Marketplace by obstinate on Wednesday March 29, 2017 @02:44PM (#13989308)
I suppose it depends on what operations you do on your table and what your query stream looks like. It's hard to imagine compute being the bottleneck for most SQL workloads . . .
Re:SQL on Distributed GPUs now available on AWS Marketplace by threeseed on Wednesday March 29, 2017 @06:23PM (#13991187)
SQL is an overloaded term these days.

There are plenty of SQL queries happening on non-database platforms e.g. Spark, Impala all of which are entirely CPU bound.

Re:SQL on Distributed GPUs now available on AWS Marketplace by qeternity on Wednesday March 29, 2017 @03:31PM (#13989774)
For OLAP use cases, CPU is most often a bottleneck...
Re:SQL on Distributed GPUs now available on AWS Marketplace by user5994461 on Wednesday March 29, 2017 @05:43PM (#13990873)
Doesn't OLAP implies branching/conditions? GPUs are terrible at evaluating if.
Re:SQL on Distributed GPUs now available on AWS Marketplace by arnon on Wednesday March 29, 2017 @05:53PM (#13990958)
OLAP is implied as a catch-all for analytics in this case
Re:SQL on Distributed GPUs now available on AWS Marketplace by Wheaties466 on Wednesday March 29, 2017 @03:11PM (#13989592)
On a Postgresql query before version 9.6 is limited to a single CPU core.

Depending on the amount of data it has to query it absolutely can take forever.

Re:SQL on Distributed GPUs now available on AWS Marketplace by user5994461 on Wednesday March 29, 2017 @05:44PM (#13990886)
Consider a paid database if that's what you need. It's not new that postgre has some limitations compared to the SQL servers/Oracle.
Re:SQL on Distributed GPUs now available on AWS Marketplace by qeternity on Wednesday March 29, 2017 @03:32PM (#13989779)
Even now, it's only multicore when doing full table scans (iirc...)
Re:SQL on Distributed GPUs now available on AWS Marketplace by jasonmp85 on Wednesday March 29, 2017 @05:01PM (#13990558)
True (see here: https://www.postgresql.org/docs/9.6/static/parallel-plans.ht... ), but in PostgreSQL 10 there are Parallel Bitmap Heap Scans and Parallel Index Scans (see here: http://rhaas.blogspot.com/2017/03/parallel-query-v2.html ).