THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
gchisto is a useful tool for analyzing GC logs https://gchisto.dev.java.net/
Additionally you can use 'jstat' on a running jvm to gain more insight into realtime GC activity, see: http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstat.html
This issue can be resolved in a few ways:
...
- Verify that logging isn't at DEBUG.Check your log4j.properties file and change the line log4j.rootLogger=DEBUG, ROLLINGFILE to log4j.rootLogger=WARN ROLLINGFILE. Logging to disk on every action can greatly effect performance.
- Verify that you are using fast local disk for the journal.
- Test with http://github.com/phunt/zk-smoketest. This should identify real performance along latency issues. It is built against 32 bit python.