Pam Ochs 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. > > You might consider getting the dtrace/troubleshooting book and running that on the system/app to see where it's bottlenecks are, though it sounds to me like you've already determined the bottleneck is cpu (which is among the easier things to fix by throwing money at it)
_______________________________________________ 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/
