Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mbuda
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
mbuda
4y ago
A. If you take a deeper look, the benchmarking part is implemented in C++ (client + benchmark session management + measurements), Python is just layer on top to orchestrate everything but it's not on a critical path at all B. Yes, old
32.
▲
by
mbuda
4y ago
There are few reasons: * platform has all the software included (memgraph, lab, mage), most of the image size are actually mage deps * at the moment we start building for ARM, the image also grow in size -> we are still figuring out how
33.
▲
by
mbuda
4y ago
Fair point, but it's not only that, there are many differences, it's mostly impossible to put 2 different systems in a fair config state, it's more about how different systems operate with certain configs / in certain en
34.
▲
by
mbuda
4y ago
Yep, from the business perspective that's by far the biggest concern :D
35.
▲
by
mbuda
4y ago
Perfect!
36.
▲
by
mbuda
4y ago
I'm not sure I understand the part about corruption. How would data in memory become corrupted? How Memgraph currently works, it stores data in memory, and async starts writing data to disk in small data chunks called deltas, later the
37.
▲
by
mbuda
4y ago
Excellent observation/question :D It depends; sometimes, it's worth it, and sometimes it is not (as always with tradeoffs). Graphs are a bit specific because most of the traversals or expensive graph analytics like PageRank touch
38.
▲
by
mbuda
4y ago
If you are asking about Memgraph in general, overall it's a graph storage + analytics system. DGraph is probably more on the pure storage side, while Memgraph is more about graph analytics (in-memory graph storage but it also stores da
39.
▲
by
mbuda
4y ago
Is there any interest in detailed comparison between C++ and Rust when it comes to different tradeoffs when implementing/using the query modules?
40.
▲
by
mbuda
4y ago
It's not, it's also based on d3 (like Neo4j viewer I think), but build from from 0
41.
▲
by
mbuda
4y ago
https://github.com/cosmograph-org/cosmos seems super nice! Yep, it's amazing to see better and better tooling around!
42.
▲
by
mbuda
4y ago
Yep, the history here is that we tried out a couple of standalone tools with the appropriate license (e.g., VisJS, which is a great library), but nothing was suitable after some point, and then the best thing was to build. You learn more +
43.
▲
by
mbuda
4y ago
Check out the Github repo https://github.com/memgraph/orb , it's Apache-2, with a lot of thinking around the software design :D
44.
▲
by
mbuda
4y ago
+ Have you seen https://github.com/cosmograph-org/cosmos ? Looks like a really scalable thing :D
45.
▲
by
mbuda
4y ago
Graphistry is really cool but the point here is not to compete on the visualization side, we needed a tool that scales for a few of our use-cases (mostly as a highly configurable graph visualizes) + a library that can easily be extended :D
46.
▲
by
mbuda
4y ago
Very good points!
47.
▲
by
mbuda
4y ago
Nice observation! That sleep is there in the case the queue is full, which means the caller can't put an additional element into it. The only option is to wait and see if the queue becomes less full... The hard question is for how long
48.
▲
by
mbuda
4y ago
Correct, but with a DB involved, there are additional benefits. This implementation is still rudimentary, but there are many options for tighter integrations, e.g., a specialized DB index that will copy data to a GPU continuously, significa
49.
▲
by
mbuda
4y ago
The idea is to publish others as well at some point, probably Go will be the next one :) Which one would you like to see?
50.
▲
by
mbuda
5y ago
In global economy, everything is possible...
51.
▲
by
mbuda
6y ago
We'll probably put the replication feature in the Memgraph Community soon. At that point, we'll make a PR to the Jepsen repo with all our tests included + yea, additional testing will be possible. That's always good. As they
52.
▲
by
mbuda
6y ago
We implemented Raft as a C++ library from scratch. We can probably publish that as s standalone implementation (open-source it). The main problem was the write performance and network communication overhead, even for read queries. There are
53.
▲
by
mbuda
6y ago
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 prov
54.
▲
by
mbuda
6y ago
Yea, we're still discussing the exact roadmap on this side. In the short term, the plan is to integrate better with the whole ecosystem. We are still exploring options on the graph NN side. Do you have any specific algorithms to point
55.
▲
by
mbuda
6y ago
Thank you! So far, Memgraph offers and supports C/C++ library ( https://github.com/memgraph/mgclient ) and Python binding ( https://github.com/memgraph/pymgclient ). Node.js is going to come shor
56.
▲
by
mbuda
6y ago
Thank you! Memgraph has built-in BFS, DFS, and weighted-shortest path. These can leverage the query planning (use the details about data distribution to perform better). Since query modules are introduced, algorithms like Page Rank could be
57.
▲
by
mbuda
6y ago
Thank you!
58.
▲
by
mbuda
6y ago
The intended usage isn't that one because Memgraph is built as a server database system. The communication has to go via the binary protocol. But, because Memgraph is implemented in C/C++ and there is the C API for the query modul
59.
▲
by
mbuda
6y ago
Memgraph supports more than 80% of openCypher TCK scenarios ( https://github.com/opencypher/openCypher/tree/master/tck ). For more details about the actual differences, please take a look here https:
60.
▲
by
mbuda
6y ago
Yes, Memgraph has an embedded Python interpreter so you can run any NetworkX graph algorithm or any other Python code. The code has access to the whole graph, so a bunch of options exists. The entire Python integration is still in the early
More ›