On 27 Jan 2012, at 13:31, Sanne Grinovero wrote: > My experiments where using the default JVM settings regarding compile > settings, with these others: > > -Xmx2G -Xms2G -XX:MaxPermSize=128M -XX:+HeapDumpOnOutOfMemoryError > -Xss512k -XX:HeapDumpPath=/tmp/java_heap > -Djava.net.preferIPv4Stack=true -Djgroups.bind_addr=127.0.0.1 > -Dlog4j.configuration=file:/opt/log4j.xml -XX:+PrintCompilation > -Xbatch -server -XX:+UseCompressedOops -XX:+UseLargePages > -XX:LargePageSizeInBytes=2m -XX:+AlwaysPreTouch > > And it's with these options that after 30 minutes of full-stress it's > still not finished warming up all of Infinispan+JGroups code. > After that I stated I was going to *experiment* with > -XX:CompileThreshold=10", to see if I could get it to compile in a > shorter time, just to save me from waiting too long in performance > tests. It doesn't seem to matter much, so I'm reverting it back to the > above values (default for this parameter for my VM is 10000).
That's surprising, I'd say that in 30 mins of invocations all the critical paths are touched much more many times than 10000. E.g. the number of reads/sec is in thousands (20k on the cluster lab). Might be that this param is ignored or it collides with other -XX ? _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
