Yes, the file system cache that lives outside the JVM heap.
Thanks for your reply - it's really helped me out. I understand now that
the OS is caching the file system cache between restarts of the Neo4J JVM.
For my use case I think I will have to have think about the best strategy
for warming the cache in the event of a full OS restart (although hopefully
this would be a rare event :))
On 5 December 2011 16:53, Mattias Persson <matt...@neotechnology.com> wrote:
> You're referring to the file system caches managed by the operating system,
> right? That neo4j has no control over and is up to the specific OS you run
> it on.
>
> 2011/12/5 Ian Forsey <for...@gmail.com>
>
> > Thanks Mattias,
> >
> > I'll try that out.
> >
> > Playing about, I've noticed that the file buffer cache seems to survive
> > restarts. Is this correct? Is it guaranteed that the whole file buffer
> > cache will survive?
> >
> > On 5 December 2011 14:09, Mattias Persson <matt...@neotechnology.com>
> > wrote:
> >
> > > Warming up the graph is best done by warming up the graph, so to speak.
> > > Every warmup use case is different, and for warming up the entire graph
> > > you'll have to loop through all nodes and get their relationships and
> if
> > > you'd like to have properties in there too then load them also. The
> most
> > > basic being:
> > >
> > > for ( Node node : db.getAllNodes() ) {
> > > IteratorUtil.count( node.getRelationships() );
> > > }
> > >
> > > Or in 1.6.M01 you can do:
> > >
> > > for ( Node node : GlobalGraphOperations.at( db ).getAllNodes() );
> > > for ( Relationship rel : GlobalGraphOperations.at( db
> > > ).getAllRelationships() );
> > >
> > > pro here is that reading the store sequentially (0-max) is faster than
> > > random access. But the list of relationships each node have isn't
> loaded
> > > this way, only the relationships themselves. I don't know which one
> ends
> > up
> > > the best for you.
> > >
> > > 2011/12/5 Ian Forsey <for...@gmail.com>
> > >
> > > > Hi there,
> > > >
> > > > I'm looking to get my entire graph into memory.
> > > >
> > > > I've configured the file buffer cache, but nodes/rels don't get added
> > > into
> > > > the cache until I first query them. Is it just a case of traversing
> the
> > > > entire graph to warm-up the cache on application startup? Or is there
> > > > another way to tell neo4j to load the entire graph into memory on
> start
> > > up?
> > > >
> > > > Thanks
> > > >
> > > > Ian
> > > > _______________________________________________
> > > > 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
> > >
> > _______________________________________________
> > 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
>
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
