There will indeed be a performance impact in your scenario. The relationship store doesn't order the relationships, so all relationships attached to Node (A) will be read. Maybe indexed relationships is an option for you, see: https://github.com/peterneubauer/graph-collections/wiki/Indexed-relationships Niels
> From: romiko.derby...@readify.net > To: user@lists.neo4j.org > Date: Tue, 12 Jul 2011 22:33:05 -0700 > Subject: [Neo4j] performance relationships > > Hi, > > If I have a Node (A) with over 50000 relationships outgoing - > RelationshipTypeA > If I have the same Node (A) with 100 relationships outgoing - > RelationshipTypeB > > Will there be a performance impact for queries travsersing RelationshipTypeB > because there are over 50000 relationships irrespective on relationship types > or does Neo4J optimise the traversing by filtering/indexing the relationships. > > I would like to know for which specific scenarios to use a category node to > group data that will be large over time. > > Regards > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
