Live data from Hacker News

Memgraph DB 1.1

memgraph.com

1–10 of 12 posts

Re: Memgraph DB 1.1

#2
Hey HN!

We've just released this blog post exploring some of the changes we made over the past few years that helped us reduce memory usage by as much as 50% and improve throughput towards near-linear scalability.

We'd love to get your thoughts.

Cheers!

Re: Memgraph DB 1.1

#4
post #3

It would be interesting to see how these benchmark results compare to other graph databases like neo4j.

That's a good point. Benchmarking different systems is always tricky to get right, but we'll get something out soon.

The focus of these benchmarks was to explain to our existing community how we improved things and share with the broader software engineering community has worked for us in the hope it could help others working on graph projects.

Re: Memgraph DB 1.1

#5
post #4
post #3

It would be interesting to see how these benchmark results compare to other graph databases like neo4j.

That's a good point. Benchmarking different systems is always tricky to get right, but we'll get something out soon. The focus of these benchmarks was to explain to our existing community how we improved things and share with the broader software engineering community has worked for us in the hope it could help others working on graph projects.

Try to include Dgraph, if it's similar (I'm not familiar with Memgraph).

Re: Memgraph DB 1.1

#6
post #5
post #4

Earlier quoted context omitted.

That's a good point. Benchmarking different systems is always tricky to get right, but we'll get something out soon. The focus of these benchmarks was to explain to our existing community how we improved things and share with the broader software engineering community has worked for us in the hope it could help others working on graph projects.

Try to include Dgraph, if it's similar (I'm not familiar with Memgraph).

Dgraph is actually very different on many aspects like data model, query language, even overall focus & target use-cases.

In my opinion it will be tricky to have a fair comparison. You can have a look at the benchmarks they published against Neo4j. It seemed like there was a lot of disagreements on both side.

What other graph databases would you like us to have a look at?

Re: Memgraph DB 1.1

#7
post #2

Hey HN! We've just released this blog post exploring some of the changes we made over the past few years that helped us reduce memory usage by as much as 50% and improve throughput towards near-linear scalability. We'd love to get your thoughts. Cheers!

I just tried to use it via the Java API (using the dockerized memgraph and neo4j driver, as indicated in your page), but there seems to be some SSL issues (self-signed certs). If I disable the SSL when running memgraph, it seems to connect, but the neo4j driver complains about it being an "unknown server". These checks are present in the newer neo4j drivers.

Is the Java API supposed to be used with an older neo4j driver?

Re: Memgraph DB 1.1

#8
post #2

Hey HN! We've just released this blog post exploring some of the changes we made over the past few years that helped us reduce memory usage by as much as 50% and improve throughput towards near-linear scalability. We'd love to get your thoughts. Cheers!

I just tried to use it via the Java API (using the dockerized memgraph and neo4j driver, as indicated in your page), but there seems to be some SSL issues (self-signed certs). If I disable the SSL when running memgraph, it seems to connect, but the neo4j driver complains about it being an "unknown server". These checks are present in the newer neo4j drivers. Is the Java API supposed to be used with an older neo4j dri…

What is the exact Bolt driver version? Memgraph v1.1 works with Bolt v1, and the last working version of Java Bolt driver is v1.6.4. Memgraph v1.2 is going to be released soon and it will include support for Bolt v4.1. Could you please provide more details about the actual setup?
Post reply on HN