// Recent 64-bit JVMs will automatically use "-XX:+UseCompressedOops". I'm not sure about your version, specifically. If you have the option, you might want to run a 32-bit JVM; it will probably run leaner and faster than a 64-bit JVM will. //
Interesting. What do you mean my faster and leaner? We're currently running 60-90 instances of tomcat on 8-core servers with 32-64GB RAM, and they all run fast. Swapping is negligible, CPU is around 20% average utilization, iowait is low. The only time we have trouble is when an instance occasionally runs out of memory and throws an OOME. When that happens, we allocate another 64MB to that instance and restart it. // If you are issuing a "kill -3" and then looking at stdout, I'd encourage you to take a look at "jstack" which can do the same thing (dump the thread status) but it can be redirected to some other file. That is, it doesn't dump to the target JVM's stdout, but the jstack tool's stdout. It's much more convenient. If you are looking for heap information, you want "jmap" instead: $ jmap -heap [pid] Unfortunately, each of these tools produces output in a slightly different format, so you may have to adjust some of your automated tools to suit. // Great info, thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
