Tim, this is a common misconception - you want warm caches, but maven or any other build system is testing cold since everything is started in a fresh JVM.
I think here there might be an option to introduce some "warmup" switch to Neo4j. In that case, Neo4j would try to fit the graph into memory before returning. Especially for small graphs, that is a good option and it really gives you a better view on the actual performance on things. Not sure what that would imply, but I will speak to the coding gods and pray for good weather ;) Cheers, /peter neubauer COO and Sales, Neo Technology 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 - Relationships count. http://gremlin.tinkerpop.com - PageRank in 2 lines of code. http://www.linkedprocess.org - Computing at LinkedData scale. On Tue, Jan 12, 2010 at 1:21 AM, Tim Langley <[email protected]> wrote: > Thank you everyone -i really appreciate all your help ;) > > (*embarassed though*) > This time it was completely my fault -i'd been benchmarking on a cold > cache - once I removed this limitation it flys > > (*embarassed again*) > > T > > Sent from my iPhone so please excuse typos adn brevity > > Tim Langley > +44 7989 539363 > > On 12 Jan 2010, at 00:12, Laurent Laborde <[email protected]> wrote: > >> On Tue, Jan 12, 2010 at 12:27 AM, Rick Bullotta >> <[email protected]> wrote: >>>> In terms of setting Java VM parameters, I know how to do it for a >>>> Java app >>> or application server, but not for Scala. ;-) >>> >>> Anyone? >> >> scala and scalac are shell script (or batch on windows). >> On my scala version, the end of the script look like this : >> >> # Reminder: substitution ${JAVA_OPTS:=-Xmx256M -Xms16M} DO NOT work >> on Solaris >> [ -n "$JAVA_OPTS" ] || JAVA_OPTS="-Xmx256M -Xms32M" >> >> if [ -z "$JAVACMD" -a -n "$JAVA_HOME" -a -x "$JAVA_HOME/bin/java" ]; >> then >> JAVACMD="$JAVA_HOME/bin/java" >> fi >> >> exec "${JAVACMD:=java}" $JAVA_OPTS -cp "$TOOL_CLASSPATH" >> -Dscala.home="$SCALA_HOME" -Denv.classpath="$CLASSPATH" >> -Denv.emacs="$EMACS" scala.tools.nsc.MainGenericRunner "$@" >> >> you can set your $JAVA_OPTS envrionment varibalbe to something like : >> JAVA_OPTS="-Xmx1024M -Xms128M" >> >> or copy scala to something like : scala-FatBurger and edit this part : >> [ -n "$JAVA_OPTS" ] || JAVA_OPTS="-Xmx256M -Xms32M" >> to : >> [ -n "$JAVA_OPTS" ] || JAVA_OPTS="-Xmx2560M -Xms320M" >> >> Btw... i'm pretty sure you run out of ram because you have a top level >> transaction. >> I sometime have the same problem, my workaround was to buy 8GB or >> ram :) >> >> -- >> Laurent "ker2x" Laborde >> Sysadmin & DBA at http://www.over-blog.com/ >> _______________________________________________ >> Neo mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
