Profiler only measures time taken by pipeline process() method,
so all preceding sitemap processing time is not available.
This includes time taken by all matchers/selectors/actions. If you do have
any havy processing in sitemap - it's not taken in account by profiler.
Your suggestions on how to improve this are welcome ;)
Vadim
> -----Original Message-----
> From: Stuart Roebuck [mailto:[EMAIL PROTECTED] (BlueYonder)]
> Sent: Saturday, July 28, 2001 4:16 AM
> To: [EMAIL PROTECTED]
> Subject: [C2+] Profiling / Log Time discrepancies
>
>
> I've just figured how to get the profiling pipelines working and very much
> appreciate the data it provides. However, I'm trying to track down a
> speed issue with a set of pages and have found that the profile generator
> indicates that the pages are processed in approx. 400ms, but the log file
> and user experience indicates 6.4secs. This happens consistently over
> repeated accesses to the same page.
>
> It appears there is some significant processing happening outside of the
> profiled zones of the ProfileGenerator and associated code.
>
> Any thoughts?
>
> Stuart.
>
> -------------------------------------------------------------------------
> Stuart Roebuck [EMAIL PROTECTED]
> Lead Developer Java, XML, MacOS X, XP, etc.
> ADOLOS <http://www.adolos.com/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
