Hi, I think the easiest way would be for you to instrument the code in org.neo4j.kernel.impl.core.NodeManager (check for nodeCache.get and relCache.get calls).
Another way would be to let the application run the same traversal/query many times in a row with different heap sizes. If later iterations of the same traversal are not converging towards the same time (faster than a cold run) there may be a problem with the JVM settings and/or kernel configuration. Regards, -Johan On Thu, Feb 18, 2010 at 5:37 PM, Georg M. Sorst <[email protected]> wrote: > Hey list, > > what would be the best way to obtain cache statistics from Neo4j, stuff > like hit / miss ratio for the node / relationship cache etc. I guess I > could always try profiling and check for the relevant methods but is > there a better way? > > More generally speaking, if your application is slow and you suspect the > cache might have something to do with it how would you proceed? While > there is some info about configuring the cache and some rough guidelines > on the recommended sizes I could not find a way to get hard numbers for > tuning. > > Thanks and best regards, > Georg _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
