Does anybody have any tips on profiling a witango application? I've got a very complicated combination of things going on in my CMS, and I'm pretty sure there's nothing I can do about the slow performance I get with multiple concurrent requests, but I'd like to see if there is any "low hanging fruit" i can grab to help optimize this application.
I can't think of a way to profile the code... (identify % of code executed in various parts of the cms engine) Has anybody ever had to do this sort of thing with Witango? Whats disturbing to me is that I have some very basic logging ability in the application that can tell me how much time I spend working with a particular javabean (to do xslt transformations) What's weird, is that when the server is loaded 16 simultaneous requests. The overall "page build time" rises a lot. But the time spent doing those xslt tranformations in the Java Bean doesn't rise nearly as much. Something causes witango to slow down a lot more. I thought about turning on debugging and parsing the results to do my own profiling, but the problem with that, is that with debugging turned on, performance problems seem to get even worse, so I'm not getting an accurate measurement of what's going on. Anyway, just thought I'd throw it out there... See if anybody has tried to do this before. -- /John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
