BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
blog.blazingdb.com
BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
1–10 of 38 posts
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#2I don't know much about how this would work or make sense, but is there a benefit to using a GPU based database with something computationally demanding like machine training / learning that uses GPUs too for computation?
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#3Congratulations on your raise! I can see many applications for this in healthcare and government. Would love to hear more about how others are implementing BlazingDB and the problems they are solving.
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#4Great to see more competition in GPU+DW space! Some questions:
1. How does BlazingDB compare to MapD ?
2. How do you skip ingest - are you using Apache Arrow like Dremio as an efficient data representation format?
3. Do you have any benchmarks, or maybe where would you see BlazingDB on this list? http://tech.marksblogg.com/benchmarks.html using same hardware as MapD ?
4. Can you run your solution in a cluster? :)
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#5Great to see more competition in GPU+DW space! Some questions: 1. How does BlazingDB compare to MapD ? 2. How do you skip ingest - are you using Apache Arrow like Dremio as an efficient data representation format? 3. Do you have any benchmarks, or maybe where would you see BlazingDB on this list? http://tech.marksblogg.com/benchmarks.html using same hardware as MapD ? 4. Can you run your solution in a cluster? :)
1) We are focused on the data lake. We love MapD, they are doing kick ass stuff, we are focused more on operating on information from disk and from cloud storage services like s3 or hdfs implementations.
2) We read parquet files into our own caching system. We often use arrow apis though do not rely on arrow for our data representation.
3) We have made client side benchmarks but have not performed a standardized replicable benchmark for people to validate yet. We have been a VERY small team to date and are going to make that available as soon as we can. You CAN launch AWS marketplace blazing instances to see how it performs.
4) You sure can. A large part of BlazingDb's focus is on distribution. You can add nodes during runtime.
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#6I don't know much about how this would work or make sense, but is there a benefit to using a GPU based database with something computationally demanding like machine training / learning that uses GPUs too for computation?
So if there are already gpu nodes being used for a machine learning workload then having blazing running on the same cluster woud allow you to share those resources. So you could run blazingdb on the same cluster as a machine learning workload and have it either feed that machine learning workload or accelerate some other sql analytics workload. This would allow you to keep your hardware in a state of greater utilization.
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#7Congrats Rodrigo! Go BlazingDB!
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#8Congrats Rodrigo and the BlazingDB team, You guys has come so far since the TechCrunch, Great Job! I really felt the chemistry the culture and the talent in your team when I met you guys in TechCrunch Battle Field!
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#9Secret source. Sorry, you don't get my data. The world has moved on.
Re: BlazingDB Origins, oh and we just raised $2.9M from Nvidia and Samsung
#10Congrats Rodrigo and team! We at MapD look forward to continued collaboration with you guys on the GOAI project and elsewhere!