Hi Pam, On Thu, May 28, 2009 at 8:31 AM, Pam Ochs <[email protected]> wrote: > Wow, lots of great stuff here, thank you!! > Status update - we had another bad day, and the cron job that my > colleague set up was still capturing data, so I was able to examine > counters during the times I knew that the application was slow. At > those times the java process was chewing up the CPU. So it looks like > the application, which isn't surprising. > Nobody wants to invest much in making changes to the current app, > since the replacement is due out next year, so I've been asked to do > whatever I can with Weblogic/Solaris etc to optimize what we have. We > are about to move to new hardware, which will put Oracle on a > different server, which may help. I haven't gotten a clear answer on > whether we will have more CPUs. > I have Weblogic Diagnostic Framework. Still trying to figure out > what to do with that. > If I can find out where the performance issues are in the app for the > benefit of the developers working on the new version, that would be a > bonus. > > -Pam > _______________________________________________ > Discuss mailing list > [email protected] > http://lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ >
I was about to suggest dtrace when I saw Doug's response. Another tool that you could use since this is a Java app is BTrace. It is a dynamic tracing tool for Java, the project page is here: https://btrace.dev.java.net It sounds like it could be helpful. There is a good write-up of it here: http://blog.igorminar.com/2008/06/btrace-dtrace-for-java.html Gary _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
