Guillaume, please try to reduce the memory mapped settings I provided, e.g by 30%. You can also inspect your system how much "free" memory is reported when you're running the neo4j test. This amount of memory can be added to the memory mapped file caches.
Have you looked at the linux transaction test? I see the only problem with your use-case if you traverse the graph in a way that constantly churns all the nodes + relationships through the caches so that they get removed before the next cache hit can occur. Michael Am 09.10.2011 um 14:50 schrieb Guillaume ALLEE: > Hi, > > 1) I had a problem with my cache warm up code which was not working. > Now with the default cache properties, I am traversing 110 relations per > millesecond. > > 2) When I load my db with your cache properties, I have MappedMemException. > See here the full stack. http://pastebin.com/XwV41iJB > I tried to put lower values, but I get the same. > FYI My heap size is 2500M. > > I do not get the algorithm to put correct values in the cache properties. > > Is 110 rels per milliseconds a good value or can I do much better ? > > About the graphDB generator : my code only imports 'real' data that are > extracted from an RDBMS. Since those data are confidential, I cannot send > them to you. > > Also FYI I get a 404 on > http://docs.neo4j.org/chunked/snapshot/configuration.html > > Cheers. > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Big-Traverser-perfomance-are-23-rels-per-milliseconds-good-tp3400711p3407300.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.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
