News for hackers. Stuff that matters.
Re:DGraph – Scalable, Distributed, Low-Latency, High-Through... by lmeyerov on Sunday March 20, 2016 @11:37PM (#11326071)
AFAICT, Titan is effectively dead, being replaced by Datastax Graph. Likewise, Blazegraph is about graph computation (think Spark's GraphX, OLAP) rather than simple reads/writes (OLTP). Systems can try to straddle both, but the benchmarks should be different.

Quickly looking at this project suggests it's on the OLTP side, not OLAP, so apples/oranges. Claiming more performance than a GPU compute engine would need some real benchmarking ;-)

Re:DGraph – Scalable, Distributed, Low-Latency, High-Through... by nl on Monday March 21, 2016 @12:55AM (#11326307)
Blazegraph is about graph computation (think Spark's GraphX, OLAP)

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/

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.

Re:DGraph – Scalable, Distributed, Low-Latency, High-Through... by lobster_johnson on Monday March 21, 2016 @11:21AM (#11328672)
There's quite a lot of activity on http://github.com/thinkaurelius/titan for a dead project. Admittedly, the issues are piling up, but the code seems to be actively worked on.