If there was one bit of wisdom on "performance" I learned in that time, is your bottleneck is likely in THE LAST PLACE, the LEAST obvious place you would expect. Everything is conjecture till you measure, measure, measure. Your better off with a clean design, then attack the slow parts.
13.8.13
12.8.13
11.8.13
-XX:-DisableExplicitGC or -XX:+DisableExplicitGC
- Java HotSpot VM Options
- java - Setting -XX:+DisableExplicitGC in production: what could go wrong? - Stack Overflow
- WebSphere Application Server Version 7.0
- Bug ID: JDK-4957014 Typo in the JVM HotSpot Options(-XX:-DisableExplicitGC)
- Oracle Technology Network for Java Developers
- Calling System.gc() is a bad idea - Java-Monitor Forum
Subscribe to:
Posts (Atom)