Gautam, look at http://docs.neo4j.org/chunked/snapshot/configuration-caches.html for some high-level information on caching. Does that meet your needs or is there more you want to know?
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Wed, Aug 31, 2011 at 9:31 PM, Gautam Thaker <gautam.h.tha...@lmco.com>wrote: > On 8/31/2011 2:39 PM, Rick Bullotta wrote: > > What is probably happening is that the relationship references might be > concentrated around a couple of nodes, forcing a large number of them to be > in memory. > > > > I can't really tell without understanding the model and how you're > "randomizing" relationships. > > > well, with 1,000,000 nodes and each node having exactly one relations to > a randomly chosen other node, it would be very unlikely for a node to > have >10 to 20 relationships. > In any event, is there an explanation some place of exactly what stays > in memory and what is on the disk in the datastore when my graph gets > big like this? What can I do minimize the amount of java heap used? > > Gautam > > _______________________________________________ > 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
