I am sorry, I really should have thought of that!, here we go:-)
my system is:
-------------
- dual Pentium 1ghz
- 4 gb ram
- 2 speedraided ldv 9gb scsi disks
- linux slackware 8
- sun sdk 1.3.1
- tomcat 3.2.3
- xalan 2.2.d9
- xerces 1.4.3
wget timing:
------------
first run of "toc.html" -> 41.879s
second run of "toc.html" -> 0.013s (!!!)
first run of "page.html?xpath=//*[@id='1222']" -> 58.031s
second run of "page.html?xpath=//*[@id='1222']" -> 0.017s (!!!)
questions:
----------
as you can see the cache works great for a few pages, but the first hit
takes a lot of time, so is it possible to hit every page at startup so the
first visitors don't have to suffer?
how can I tune my cache settings? I have tried with this:
<store class="org.apache.cocoon.components.store.MRUMemoryStore">
<parameter name="freememory" value="1000000"/>
<parameter name="heapsize" value="600000000"/>
<parameter name="cleanupthreadinterval" value="10"/>
<parameter name="maxobjects" value="100"/>
<parameter name="usecleanupthread" value="true"/>
<parameter name="threadpriority" value="5"/>
<parameter name="filesystem" value="true"/>
</store>
but it doesn't really cut the cheese, after a some usage the site starts to
regenerate the pages again, and the visitors will have to wait for nearly a
minute for each call...
am I doing something wrong here?
mvh karl řie
-----Original Message-----
From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
Sent: 22. august 2001 21:53
To: [EMAIL PROTECTED]
Subject: Re: performance tuning...
Karl Řie wrote:
>
> Hi, I have a very standard pipeline for my project. The file
> "oversikten.xml" is filtered through the stylesheet
> "oversikten.xsl" which uses parameters sent to it to filter/rearrange the
> output.
>
> <map:match pattern="page.html">
> <map:generate src="sources/oversikten.xml"/>
> <map:transform src="oversikten.xsl">
> <map:parameter name="use-request-parameters"
value="true"/>
> </map:transform>
> <map:serialize type="html"/>
> </map:match>
>
> The file "oversikten.xml" is about 4mb large, and the site performs quite
> badly. Is there any tips for improving the performance short of splitting
> the file into smaller parts as this I am not allowed to do that.
What are the numbers your are targeting? (i.e. how fast do you need it?)
What kind of hardware are you using?
What are the current numbers you are getting? (i.e. how slow is it now?)
To really help you, we need these questions answered.
If you are using the Caching Pipeline, you should be able to experience
better
performance each time you request it. However, if your cache is set too
small
to keep the entire XML in memory, the cache will be of no benefit.
How complicated are the XSLT stylesheets? If you are not using global
variables
or parameters, that speeds things up.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
