Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Performance and Sitemaps
Date: Wed, 26 Jul 2006 16:55:34 +0200
Message-ID: <A955EA1F8FE31749AEC8C998082F6C7CBA906E@hai01.hippo.local>
Thread-Topic: Performance and Sitemaps
Thread-Index: AcawvTFRPjnaV3XPQwWpxqbPaxre7AABXdQA
From: "Ard Schrijvers" <a.schrijvers@hippo.nl>
To: <users@cocoon.apache.org>


> Hi there,
>=20
> I've been trying to increase the performance of my cocoon=20
> deployment and the profiler has shown me that the pipeline=20
> seems quite fast but the over all time is much slower than=20
> the time in each of the components in the pipe. When I was=20
> playing with a different bit of the site I noticed that it=20
> was much faster and was wondering if it might have been=20
> something to do with the size of the sitemap in both cases.=20
> One of the main areas of my site has a very large sitemap=20
> (about 1500 lines, 22 pipelines and  80 matchers). Would this=20
> results in a noticeable performance it? If not can you think=20
> of anything the profiler might not include in its timings?

I never noticed a correlation between a large sitemap and performance =
(though sitemaps of 1500 lines I do not like very much, but that is =
something else :-) )

Anyway, it is not strange that some parts are faster then others. It =
just depends on what a specific part does. Does it get an xml file from =
repository via http or webdav or whatever, is it a large file, are there =
complex xsl's (complex for a computer, like counting all nodes in an xml =
all the time, or going to parent ancestor next sibbling the previous and =
the back to the root..)

Anyway, I don't use profilers to find my slow pieces. I do it from a =
10.000 kilometers above view. In my opinion this works best. I record a =
page request with solex (eclipse plugin) and count the time it takes to =
get the file again (after a clear cache or before, just what you want to =
measuer). Then, I start commenting sitemap parts. Within 30 sec you will =
find any performance flaw, guaranteed.

Then, I don't know what you consider slow. Are you talking about slow =
the first time, slow when cached? Slow =3D 2 sec or 200 ms?=20

Regards Ard

>=20
> Thanks,
>=20
> Gary
>=20
> *****************************************************************
> The information contained in this message may be confidential or=20
> legally privileged and is intended for the addressee only. If you=20
> have received this message in error or there are any problems=20
> please notify the originator immediately. The unauthorised use,=20
> disclosure, copying or alteration of this message is=20
> strictly forbidden.
> *****************************************************************
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>=20
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org