Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of project? #33

Open
joshcho opened this issue Dec 2, 2022 · 9 comments
Open

Status of project? #33

joshcho opened this issue Dec 2, 2022 · 9 comments

Comments

@joshcho
Copy link

joshcho commented Dec 2, 2022

I have taken a keen interest in this project; I have a small project and have both a vivace-graph version and a neo4j version, with significant speedup with vivace-graph version, so much so that I 'm willing to work with a largely unmaintained project. What are the authors' plan with this project? I am curious.

@kraison
Copy link
Owner

kraison commented Dec 2, 2022

Hi Josh. I am currently volunteering in Ukraine and rarely have power or internet, much less time to code. Once this war is over, I will get back to maintaining VG. I am happy to support you as much as I can in the meantime, given my current situation.

@joshcho
Copy link
Author

joshcho commented Dec 2, 2022

Thank you very much. Best of luck, I will submit pull requests in the meantime that may be helpful.

@joshcho
Copy link
Author

joshcho commented Dec 3, 2022

I am building something that requires a graph for each user. Would you recommend (in terms of speed and otherwise) having a user's graph be a subgraph of one large graph, or having a graph for each user? I haven't been able to get the latter to work.

Also, I noticed each graph is more than 2GB, which might hinder the multi-graph approach (though isolation would be really nice).

@kraison
Copy link
Owner

kraison commented Dec 3, 2022

Multiple graphs is not an intended use case. It might work, but linking nodes between graphs definitely won't work as I suspect you intend.

@kraison
Copy link
Owner

kraison commented Dec 3, 2022

Because this is a Lisp-based project, there are certain lines of demarcation that we are used to using that just don't fit. The best way to understand VG is not as a database separate from your code, but rather as a file-backed Lisp heap with user-defined indexing of objects. I highly recommend this book as one reference: https://en.m.wikipedia.org/wiki/The_Art_of_the_Metaobject_Protocol

@joshcho
Copy link
Author

joshcho commented Dec 3, 2022

I have that book open on one of my tabs, this gives me more motivation to read it. Thanks!

@joshcho
Copy link
Author

joshcho commented Feb 4, 2023

How do you estimate the performance would look like if you have, say ~100M nodes and ~100M edges?

@tluyben
Copy link

tluyben commented Jul 9, 2023

@kraison @joshcho Maybe until your return, there can be a maintained fork ? @joshcho did some good work, so maybe that's a good start.

@joshcho
Copy link
Author

joshcho commented Dec 24, 2023

I made one or two changes, so I don't think they are good enough. Also unfortunately, I have moved onto other projects, so won't be of much help here.

Best of luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants