You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Richard Frovarp <ri...@sendit.nodak.edu> on 2008/09/05 23:43:30 UTC
Performance tuning
I'm starting to have some performance issues and I'm trying everything I
can to get past them.
I do have httpd serving out my css, javascript, and images in the css to
bypass tomcat.
Anyone have any updated or better documentation for configuring ehcache
than what we have on our website? I just looked, my cache file is 4.0
GB. I run a lot of publications, but that still seems unreal and is
probably hurting me. I'm running our recommended settings from the
production check list. What is going on here?
Also, anyone doing caching via httpd's mod_cache functionality?
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Performance tuning
Posted by Jann Forrer <ja...@id.uzh.ch>.
Hi Richard
[ ... ]
>
> I've updated docu. I need to figure out how to get that into svn now.
> The key is that we were changing the ehcache.xml file. That only
> provides defaults for caches created with only a name, not a list of
> parameters. Cocoon creates caches with a list of parameters, with the
> hard coded defaults set the same as the shipped ehcache.xml. However, to
> actually set those values, you must change the cocoon.xconf file where
> EHDefaultStore gets its values from. I don't have anything overflowing
> to disk, so it must be expiring. Otherwise I generate about 700 MB in
> overflow in a day starting from an empty cache. I did up my maxobjects
> to 30,000 to keep more in memory, but that can't account for the
> dramatic drop. Plus I do finally see the expire thread running under
> tomcat using jconsole.
>
Thanks very much for updating the docu. I will try to configure our
cache based on your recommendation.
Jann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Performance tuning
Posted by Richard Frovarp <ri...@sendit.nodak.edu>.
Richard Frovarp wrote:
> Jann Forrer wrote:
>
>> One problem is that we use a quite old version of ehcache. I think it is
>> 1.2. It seems that certain parameter as e.g. eternal
>> are not available for cache configuration in this version:
>>
>> http://www.terracotta.org/confluence/display/integrations/EHCache+generic
>>
>>
>> At least we configure ehcache with eternal = false but that has no
>> effect :-(
>>
>> HTH
>>
>> Jann
>>
>>
> Yeah, changing it in the ehcache.xml file does not affect the cache,
> only the cache manager (or something like that). It has to be changed
> in the cocoon.xconf file, then it works. I wanted to give my setup a
> couple more days to make sure it was functioning properly before
> documenting it. Everything looks good, so I should be able to get it
> up today in docu.
>
> Richard
I've updated docu. I need to figure out how to get that into svn now.
The key is that we were changing the ehcache.xml file. That only
provides defaults for caches created with only a name, not a list of
parameters. Cocoon creates caches with a list of parameters, with the
hard coded defaults set the same as the shipped ehcache.xml. However, to
actually set those values, you must change the cocoon.xconf file where
EHDefaultStore gets its values from. I don't have anything overflowing
to disk, so it must be expiring. Otherwise I generate about 700 MB in
overflow in a day starting from an empty cache. I did up my maxobjects
to 30,000 to keep more in memory, but that can't account for the
dramatic drop. Plus I do finally see the expire thread running under
tomcat using jconsole.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Performance tuning
Posted by Richard Frovarp <ri...@sendit.nodak.edu>.
Jann Forrer wrote:
> Hi Richard
>
>
> I made some tests with mod_cache. Our problem was that i could not
> delete mod_cache entries (from our authoring environment), so that the
> publish workflow has no direct effect on the live page but you have to
> wait until the cache entry expires.
> If you can live with that drawback mod_cache certainly is a good and
> fast solution
>
>
>
Thanks for the information. I'll have to look into it some more.
> One problem is that we use a quite old version of ehcache. I think it is
> 1.2. It seems that certain parameter as e.g. eternal
> are not available for cache configuration in this version:
>
> http://www.terracotta.org/confluence/display/integrations/EHCache+generic
>
> At least we configure ehcache with eternal = false but that has no
> effect :-(
>
> HTH
>
> Jann
>
>
Yeah, changing it in the ehcache.xml file does not affect the cache,
only the cache manager (or something like that). It has to be changed in
the cocoon.xconf file, then it works. I wanted to give my setup a couple
more days to make sure it was functioning properly before documenting
it. Everything looks good, so I should be able to get it up today in docu.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Performance tuning
Posted by Andreas Hartmann <an...@apache.org>.
Jann Forrer schrieb:
> Hi Richard
>
>>> I'm starting to have some performance issues and I'm trying everything
>>> I can to get past them.
>>>
>>> I do have httpd serving out my css, javascript, and images in the css
>>> to bypass tomcat.
>>>
>>> Anyone have any updated or better documentation for configuring
>>> ehcache than what we have on our website? I just looked, my cache file
>>> is 4.0 GB. I run a lot of publications, but that still seems unreal
>>> and is probably hurting me. I'm running our recommended settings from
>>> the production check list. What is going on here?
>>>
>>> Also, anyone doing caching via httpd's mod_cache functionality?
>>>
> I made some tests with mod_cache. Our problem was that i could not
> delete mod_cache entries (from our authoring environment), so that the
> publish workflow has no direct effect on the live page but you have to
> wait until the cache entry expires.
> If you can live with that drawback mod_cache certainly is a good and
> fast solution
We're using mod_cache for an application, it's blazing fast - especially
mod_mem_cache. The publishing scenario is indeed the major issue. It is
not possible (or at least not straightforward) to delete particular
pages, since a hash function is used to determine cache directory names.
You're lucky if you can publish at night (given that you have traffic
only from a limited set of time zones) and use e.g. a spider to
pre-populate the cache. If you have only a limited number of pages that
are frequently requested it might even be worth deleting the whole cache
when a page is published, since the cache will be popluated again quickly.
-- Andreas
>
>
>>> Richard
>>>
>> So it turns out our documentation does not fully identify the changes
>> needed to get the ehcache to not use eternal entries. I will try to get
>> it updated sometime this week.
>>
> One problem is that we use a quite old version of ehcache. I think it is
> 1.2. It seems that certain parameter as e.g. eternal
> are not available for cache configuration in this version:
>
> http://www.terracotta.org/confluence/display/integrations/EHCache+generic
>
> At least we configure ehcache with eternal = false but that has no
> effect :-(
>
> HTH
>
> Jann
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Performance tuning
Posted by Jann Forrer <ja...@id.uzh.ch>.
Hi Richard
>> I'm starting to have some performance issues and I'm trying everything
>> I can to get past them.
>>
>> I do have httpd serving out my css, javascript, and images in the css
>> to bypass tomcat.
>>
>> Anyone have any updated or better documentation for configuring
>> ehcache than what we have on our website? I just looked, my cache file
>> is 4.0 GB. I run a lot of publications, but that still seems unreal
>> and is probably hurting me. I'm running our recommended settings from
>> the production check list. What is going on here?
>>
>> Also, anyone doing caching via httpd's mod_cache functionality?
>>
I made some tests with mod_cache. Our problem was that i could not
delete mod_cache entries (from our authoring environment), so that the
publish workflow has no direct effect on the live page but you have to
wait until the cache entry expires.
If you can live with that drawback mod_cache certainly is a good and
fast solution
>> Richard
>>
>
> So it turns out our documentation does not fully identify the changes
> needed to get the ehcache to not use eternal entries. I will try to get
> it updated sometime this week.
>
One problem is that we use a quite old version of ehcache. I think it is
1.2. It seems that certain parameter as e.g. eternal
are not available for cache configuration in this version:
http://www.terracotta.org/confluence/display/integrations/EHCache+generic
At least we configure ehcache with eternal = false but that has no
effect :-(
HTH
Jann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Performance tuning
Posted by Richard Frovarp <ri...@sendit.nodak.edu>.
Richard Frovarp wrote:
> I'm starting to have some performance issues and I'm trying everything
> I can to get past them.
>
> I do have httpd serving out my css, javascript, and images in the css
> to bypass tomcat.
>
> Anyone have any updated or better documentation for configuring
> ehcache than what we have on our website? I just looked, my cache file
> is 4.0 GB. I run a lot of publications, but that still seems unreal
> and is probably hurting me. I'm running our recommended settings from
> the production check list. What is going on here?
>
> Also, anyone doing caching via httpd's mod_cache functionality?
>
> Richard
>
So it turns out our documentation does not fully identify the changes
needed to get the ehcache to not use eternal entries. I will try to get
it updated sometime this week.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org