Hey everyone, I'm Dave from the Memgraph Platform team. Our old Memgraph Lab implementation struggled with performance issues, so we decided to do something about that. At the moment, there are a lot of visualization options out there: some with very wide use cases, some are popular but out of date and some of them have performance issues or provide a terrible developer experience. We wanted to find the solution that would best suit us, so we started the process with an overview and benchmark.
You can find all of the details in our blog post. We would like to hear what you think about our approach and solution. If you have any questions about methodology, approach, or our findings, drop them in the comments. I'd be more than glad to answer them.
This benchmarking was one important part of our development process that has led us to a new visualization engine [1].
Neo4j uses a fork of VisJS. They call it NeoVis. We didn't go that route because vis-network is tightly coupled and has a lot of calls to the browser window reference which doesn't work in a WebWorker environment. So simulations end up blocking the main thread.
Cosmos really looks amazing when it comes to performace. Besides visual rendering on the GPU, they also do the graph layout simulation calculations on the GPU as well, which is a first. SigmaJS for example uses graphology for the calculations, and WebGL for rendering.
Hey everyone, I'm Dave from the Memgraph Cloud team. After an initial private beta phase, and lots of user feedback, we’re finally ready to unveil Memgraph Cloud to the world!
Building a cloud offering from scratch with a team of ~6 was far from easy, and I’m super proud of what we’ve achieved.
If you have any questions or feedback, I’ll be around all day to answer. Happy to share technical details, lessons learned, and anything else you might want to know. Just ask. :D
P.s. You get a 14-day free trial, but if you need more time, just ping us through the in-app chat and I’ll be happy to extend that for you.
You can find all of the details in our blog post. We would like to hear what you think about our approach and solution. If you have any questions about methodology, approach, or our findings, drop them in the comments. I'd be more than glad to answer them.
This benchmarking was one important part of our development process that has led us to a new visualization engine [1].
[1] https://news.ycombinator.com/item?id=32868091