My current time being spent on Jetspeed may be going away soon (gotta love when projects get put on the back-burner). If I can find time, I would like to hook Jetspeed up to JProbe and see what it is up to. The 80/20 rule seems to apply quite well to performance tweaking on this stuff. Don't know if anyone else has one of these profiling/performance tools, but they definitely give an interesting look at what is taking time. The biggest problem is that they don't necessarily tell you anything if you don't have an idea of what the code is *supposed to* be doing. I definitely don't have a good feel for the inner workings of Jetspeed, so I may not be able to glean much from JProbe.
I'll post any information I collect... If I don't get redirected too early. Craig -----Original Message----- From: Glenn Golden [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 3:01 PM To: Jetspeed-Dev ([EMAIL PROTECTED]) Subject: getTemp() usage I put a breakpoint in TurbineUser.getTemp() and have been watching all the getTemp calls for a single request - wow! There are many. One thing I noticed is that we seem to be building the profile many many times. Even though it's stored in the rundata! I think that the jslink needs it (in BaseJetspeedLink), so asks for it (Profiler.getProfile(rundata)), and the Profiler class just passes the request to the ProfilerService, and it just goes and creates it... Unless I'm missing something here, it seems that we could put a check in the Profiler class that pulls the profile out of the rundata, if it's there, instead of calling the service... - Glenn -------------------------------------------- Glenn R. Golden, Systems Research Programmer University of Michigan School of Information [EMAIL PROTECTED] 734-615-1419 -------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
