Loading one property on a node results in the entire property chain being loaded, i.e. if you have numeric values all properties will be loaded on the first getProperty request on that node... after that it's a HashMap lookup from the key to the value. So the first getProperty (if that node hasn't been loaded yet or it has been loaded but flushed out of the cache to make room for other more frequently used nodes) will be slow (a sequential scan through all properties), all other will be very fast.
2011/7/22 Niels Hoogeveen <pd_aficion...@hotmail.com> > > This certainly can be done with a Lucene lookup, I am just not so sure if > the lookup is actually faster. > > > From: rick.bullo...@thingworx.com > > To: user@lists.neo4j.org > > Date: Fri, 22 Jul 2011 05:41:09 -0700 > > Subject: Re: [Neo4j] Number of properties on a PropertyContainer > > > > That's a perfect use case for a super trivial Lucene index, no? Would > seem to be a much easier solution with much faster lookup...and built into > Neo4J. > > > > ________________________________________ > > From: user-boun...@lists.neo4j.org [user-boun...@lists.neo4j.org] On > Behalf Of Niels Hoogeveen [pd_aficion...@hotmail.com] > > Sent: Friday, July 22, 2011 8:21 AM > > To: user@lists.neo4j.org > > Subject: [Neo4j] Number of properties on a PropertyContainer > > > > Last night while working on some enhancements on the Neo4J API, I set up > a method to lookup the name of a relationship, to facilitate the creation of > associated nodes. > > The method I use, is to create a node (which can be found through the > reference node) and on this node create a property for each relationship > name. The value of the property is the node id of the associated node. > > My question is if this scales properly. It is unlikely any Neo4J store > will contain millions of relationship types, but it is conceivable that > there may be over ten thousand relationship types in a store. Will this > solution still work under such conditions, or is it better to create a > relationship for each relationship type and store the node id of the > associated node in the relation. > > Niels > > _______________________________________________ > > 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 > > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
