Hi,
I have the following aggregation pipeline:
<map:pipeline type="profile-noncaching">
<map:match pattern="testpage">
<map:act type="dispatchaction">
<map:aggregate
element="portalseite">
<map:part
src="cocoon:/topnav?{topnav}" element="topnav"/>
<map:part
src="cocoon:/leftnav?{leftnav}" />
<map:part
src="cocoon:/content?{content}" element="content"/>
</map:aggregate>
<map:transform
src="xslt/{pagelayout}"/>
<map:serialize type="html"/>
</map:act>
</map:match>
The "dispatchaction" provides some parameters for the aggregation parts and
provides the name of the XSLT-Template for the pagelayout. All the parts are
generated in a separate caching pipeline.
I did a stress test with JMeter and fired 20 simultanous requests. The
performance result are not very good.
Average response time is 1800 ms.
When I fire a single request I get quite good response time of 30-40 ms.
The profiling-page tells me the following:
<aggregator> Total: 1680 Setup: 1538 Processing: 142
xslt src=xslt/pagelayout_1.xsl Total: 3 Setup: 2 Processing: 1
Html-serializing Total:1 Setup:0 Processing:1
So setting up the aggregation takes most of the time. Can anyone give me a
hint about what to do to decrease this setup-time? Does the setup-time
include the processing-time of the parts?
Thanks for any suggestions
Kind regards
Ole
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
