Re:DGraph – Scalable, Distributed, Low-Latency, High-Through...
by lmeyerov on Monday March 21, 2016 @03:01AM
(#11326620)
Blazegraph has multiple backends. Their GPU compute engine vs. their classic DB engine are different ones. And yes, I doubt they use the same approach as GraphX, considering they've published how they don't (MapGraph) and GPUs require way more work. Lumping all these systems together doesn't make sense: reads aren't writes, and there's a whole world of graph computations. Benchmarks matter.
That said, I'd be skeptical of a GPU system for being great at writes, and I'd be skeptical of a non-GPU one computing better than one on GPUs.
This is definitely incorrect. Wikidata uses it exclusively for read/write queries.
The (GPU accelerated) graph processing in BlazeGraph is new, and it's pretty unclear to me if it actually does the (GraphX) style processing. The examples[1] are all query-based.
It does look interesting though!
[1] https://www.blazegraph.com/product/gpu-accelerated/