cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Michels <step...@apache.org>
Subject Re: benchmarking Cocoon?
Date Sat, 19 Apr 2003 15:33:42 GMT



On Fri, 18 Apr 2003, Stefano Mazzocchi wrote:

> on 4/19/03 9:48 AM Argyn wrote:
>
> > If anyone was thinking about it, why not discuss it. If not, then I'll
> > forget it for a while.
>
> There are a few things that need to be seriously benchmarked:
>
>  1) compiled generators vs interpreted generators
>  2) compiled transformers vs. interpreted transformers
>  3) speed of serialization
>  4) speed of multiple xslt transformation compared to a single stylesheet
>
> In short, it's very hard to tell where the hotspot of your pipeline is
> and the profiler information doesn't give you much info given the fact
> that event-driven processing can't clearly separate processing stages.
>
> One thing can be done, though: incremental profiling thru pipeline
> dissection.
>
> For example, consider a pipeline composed or
>
>  g ---> t1 ---> t2 ---> t3 ----> s
>
> the *real* timing is taken if we remove the rest of the pipeline and
> measure with 5 different requests the time taken... so
>
>  request #1) time taken to execute g --->
>  request #2) time taken to execute g --->  t1 ---->
>  and so on, until the end
>
> this is the only meaningful way to show where the time is spent.

You also use buffers between each component to measure the time, like
the ProfilerBlock do. Yes, the buffer take also time, but in almost
cases less than 1 ms.

But anyway the independent measurement within the servlet container
is difficult.

Stephan.


Mime
View raw message