2011/11/18 serge s.fedoro...@gmail.com
Are these following topics will be treated in future release (and when if
you
know) ?
1/ Supernode
I know there is a big downside in handle of super-nodes, which can be a big
issue in a twitter-like website with, for example a user followed by more
On Sat, Nov 19, 2011 at 11:20 AM, Mattias Persson
matt...@neotechnology.com wrote:
2011/11/18 serge s.fedoro...@gmail.com
Specifically what's bad about how they are handled is that to get any
relationship from a node they all have to be loaded once first into cache,
regardless of which type
2011/11/19 Krzysztof Raczyński racz...@gmail.com
On Sat, Nov 19, 2011 at 11:20 AM, Mattias Persson
matt...@neotechnology.com wrote:
2011/11/18 serge s.fedoro...@gmail.com
Specifically what's bad about how they are handled is that to get any
relationship from a node they all have to be
Great, since my schema is a tree (1 incoming, up to hundred of
outcoming) i was worried about that.
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
I don't know if a node with a hundred relationships can be considered a
super node though. Loading a hundred relationships is pretty fast and warm
nodes (all its relationships in cache) is already fast on these things. I'm
planning on maybe switch internal store representation on a given threshold
Are these following topics will be treated in future release (and when if you
know) ?
1/ Supernode
I know there is a big downside in handle of super-nodes, which can be a big
issue in a twitter-like website with, for example a user followed by more
than 200k users (i have in head, real case) or
Hi Serge,
Regarding supernodes I already opened an issue about this some time ago:
https://github.com/neo4j/community/issues/19
and as you can read there, at the end of the conversation Peter said: we
will hopefully be on it for 1.6 !
I really hope they keep thinking of fixing this for 1.6
thanks, it sounds great :)
is there a release date for 1.6 ?
--
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Scalability-Roadmap-tp3519034p3519137.html
Sent from the Neo4j Community Discussions mailing list archive at Nabble.com.
1/ Supernode
2012, around Q2.
2/ Sharding and horizontal scalability
2013, around Q1.
These are guesses not promises :-)
Jim
PS - sharding graphs is NP complete. In theory no general solution exists.
___
Neo4j mailing list
User@lists.neo4j.org
Jim,
Not to nitpick, but that's for an ideal graph partitioning, not graph
sharding overall, right? Eg the problem is solvable in many specific
domains?
- Matt
On Nov 18, 2011 1:27 PM, Jim Webber j...@neotechnology.com wrote:
1/ Supernode
2012, around Q2.
2/ Sharding and horizontal
Hey Matt,
Not to nitpick, but that's for an ideal graph partitioning, not graph
sharding overall, right? Eg the problem is solvable in many specific
domains?
You're right - it's the general case. I was just making the point that sharding
isn't something that's an afternoon's hacking to
...but I'm sure the community will come up with a wide range of sharding
patterns, code, and best practices!
On Nov 18, 2011, at 5:46 PM, Jim Webber j...@neotechnology.com wrote:
Hey Matt,
Not to nitpick, but that's for an ideal graph partitioning, not graph
sharding overall, right? Eg the
12 matches
Mail list logo
