> From: Vasanth Kumar ravi [mailto:[EMAIL PROTECTED] > Subject: Question on Performance Tuning > > We did take thread dumps while performing the test, and > found nothing related to application bottlenecks.
Thread dumps are appropriate for diagnosing hangs, but they're not terribly useful for analyzing CPU usage. You'd be better off running a profiler to see where time is being spent. Even the JVM's built-in hprof running in sample mode should give you a pretty good idea of where the cycles are going (or use JVisualVM). > Can I get some pointers on anything to be tuned in > the tomcat to reduce the cpu utilization. First, find out what's really using the CPU before fiddling with anything. Tweaking Tomcat is not likely to change much assuming the thread pool and heap are adequate for your load. You've specified several GC options that may or may not be appropriate. Unless you've proven that changing NewRatio, NewSize, MaxNewSize, and SurvivorRatio actually helps your throughput, you're likely better off leaving them alone. 128M MaxPermSize may be too small if you have a lot of classes in your webapps. Enabling concurrent GC produces more regular response times, but will actually *reduce* throughput in most cases. These might help slightly: * Remove AspectJ. * Turn off PrintGCDetails. * Remove unused webapps. * Precompile JSPs. * Turn off auto-deployment. * Turn off monitored resources. * Set the parameters for the JSP servlet (in conf/web.xml) for production. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
