John,
I know this isn't new but I read the debug. As you know I work with my clients' applications to maintain performance on my servers. A lot of what I do is isolating poorly performing areas of code and optimize them. Unfortunately for you, it's quite difficult to type out my decade of experiences in an email, but I have learned how to spot execution problems by reading the debug and looking for large time gaps between actions. I also know a number of code snippets to avoid, things that Witango does poorly, including things that slow Witango down exponentially. I've written caching routines in complex websites so that repetitive tasks are done less frequently, and I've learned certain high-performance techniques. Problem with all this is that each application and developer needs something a little different. My first suggestion is to use debug. I understand that you believe you'll be looking at skewed results, but the skew will be proportional (what's slow under debug will still be slow otherwise, as debug adds a near-equal amount of execution time to all actions of a request). Once you have a few hot spots to look at, start logging before and after times of several key bits of code. Then work on optimizing them. Oh about your Java Bean, I suspect that Java is going to execute faster/better under load than Witango due code or compiling issues between them. Robert 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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
