Hi, >> with >> a need to know which thread is taking the most CPU time, heap resources >per >> application instance, which request is hanging/taking most of the CPU >time, >> etc. I do not want to know data regarding all the installed apps on the >JVM, >> but seggregate them purely on the ones specifically under webapps. >> Hope this helps :)
Wow. That's a lofty goal -- good luck! I don't know if such a solution could really be durable and robust. Assuming that tomcat (hopefully) continues to aggressively improve performance by pre-allocting / pooling / sharing all sorts of stuff across applications, across contexts, and in the future across instances and clusters, your type of solution could never be accurate according to your own set criteria. Seems like a no-win situation? What about the approach of: - Tune instance of app on single server, using an existing tool e.g. OptimizeIt. - Then expand to multiple instances / multiple servers. Change your tool from slow, complicated profiler like OptimizeIt to lightweight performance benchmarking tool e.g. wget. - Attempt to analyze why things are behaving the way they are and fix them, going back to step one (single app, single server) as many times as needed. Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
