171–176 of 176 posts
Earlier quoted context omitted.
Why not get in touch with us and let us help you instead of dropping us?
I'm totally open to that. I'm not going to be changing anything around the suggestions any time soon, but who should I get in touch with when I do?
Gitter is a great idea in theory. In practice it's just been a place for my questions to go unanswered.
Great tool when used effectively.
Hey, what do you use neo4j for? I am interested in your use case as I have recently started using it also. Thanks!
Gitter co-founder here: we use neo4j for suggesting rooms. So, if you're in room A and room B, and most people in those two rooms are also in room C, then we suggest that you join room C. As I mentioned elsewhere, we also use some non-neo4j based methods for suggestions (including your GitHub graph). One of the problems we've had with neo4j is that we haven't been able to make it scale. It frequently burns up from be…
Earlier quoted context omitted.
You might want to reach out to Al Baker or Kendall Clark at Stardog. Their product is more RDF centric than for generic graphs like Neo4j, but is in my opinion a much better product. They have a community version, and have open sourced several pieces, but it is commercial. https://www.stardog.com/docs/ If you want pure Open Source then Titan might be a good fit for Gitter. http://titan.thinkaurelius.com/
The big problem with the way we use neo4j is around huge rooms with ~100K users. The number of possible rooms that neo4j has to traverse (even a shallow traversal) for a user in a big room is huge. Thanks for your recommendations. I'll definitely check them out.
That's why in recommendations, I usually filter them out b degree (which is a constant value read).
MATCH (r:Room) WHERE size( (r)You're also not using directions in your queries, which will also help.
I looked at your other queries, they can also be improved easily, if you want to I can help you do that. Just need some sample data or a read-only access to the db. Just ping me at michael@neo4j.com.
Earlier quoted context omitted.
As someone who has written an IRC server implementation, there is no standard protocol. There is an RFC, but no one implements it. Instead, each server uses its own mix of poorly documented pseudo-standards.
IRCv3 FTW. I don't think they'll achieve their goals before IRC completely dies, though.