cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agssa.net>
Subject Re: Cocoon Performance Woes, Is it flow? I don't know!
Date Fri, 18 Mar 2005 22:19:47 GMT
eric:

Two more tips:

Try to switch to ehcache. I hear some ratings to the slowness of jcs cache
(the default cache system in in 2.1.5.1). BTW in 2.1.6 I think the default
cache system is ehcache, one more reason to move to 2.1.6 ;_).

if posible switch from xinclude to cinclude, AFAIK still today xinclude is
not cached and cinclude can be cached. This should improve the application
performance. On the oher hand, using cinclude you are "married" with
cocoon.  All in all, I think this is not a minus for cinclude since using
other cocoon related techno you are already "married".

BTW, I am wondering about the changes you did. Helped them a little bit in
the performance or not?

Best Regards,

Antonio Gallardo.


On Vie, 18 de Marzo de 2005, 15:46, Eric E. Meyer dijo:
> Antonio Gallardo wrote:
>
>>Can you post the sizes of the returned pages in the thread? I guess this
>>is an important point too.
>>
>>
>
> The pages are roughly similar in size:
>
> home page: /
> 17.54 KB (17964 bytes)
>
> search1: /luxury_hotels/europe__france__paris/index.html
> 29.88 KB (30599 bytes)
>
> search2: /luxury_hotels/bahamas_%26_the_caribbean/beach_resort/index.html
> 29.33 KB (30037 bytes)
>
> search3:
> /luxury_hotels/europe__france__paris/city_centre_location/index.html
> 30.29 KB (31017 bytes)
>
> detail: /luxury_hotel/new_york,_ny/the_carlyle
> 25.65 KB (26267 bytes)
>
>
>>Also, consider to move to cocoon 2.1.6, now here is why:
>>
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=31760
>>
>>I saw you canged some pools inside tomcat. Did you changed some cocoon
>>pools? Did you adjusted cocoon memory usage inside cocoon.xconf?
>>
>>
> Hm - I didn't (until just now) see that there were pool sizes specified
> in the cocoon.xconf. These are the values that I have
>
>   <xml-parser class="org.apache.excalibur.xml.impl.JaxpParser"
> logger="core.xml-parser" pool-grow="4" pool-max="32" pool-min="8">
>     <parameter name="validate" value="false"/>
>     <parameter name="namespace-prefixes" value="false"/>
>     <parameter name="stop-on-warning" value="true"/>
>     <parameter name="stop-on-recoverable-error" value="true"/>
>     <parameter name="reuse-parsers" value="true"/> <!-- EM: changed-->
>     <parameter name="drop-dtd-comments" value="true"/>
>   </xml-parser>
>
>   <xml-serializer
> class="org.apache.cocoon.components.sax.XMLByteStreamCompiler"
> logger="core.xml-serializer" pool-grow="4" pool-max="32" pool-min="8"/>
>   <xml-deserializer
> class="org.apache.cocoon.components.sax.XMLByteStreamInterpreter"
> logger="core.xml-deserializer" pool-grow="4" pool-max="32" pool-min="8"/>
>
> I removed the store janitor and switched both the store and
> transient-store to Whirly Cache.
>
>   <transient-store logger="core.store.transient">
>         <backend>com.whirlycott.cache.impl.ConcurrentHashMapImpl</backend>
>         <tuner-sleeptime>10</tuner-sleeptime>
>         <!-- evicts least frequently used items when pruning -->
>         <policy>com.whirlycott.cache.policy.LFUMaintenancePolicy</policy>
>         <maxsize>10000</maxsize>
>   </transient-store>
>
>   <store logger="core.store">
>     <parameter name="use-cache-directory" value="true"/>
>         <backend>com.whirlycott.cache.impl.ConcurrentHashMapImpl</backend>
>         <tuner-sleeptime>10</tuner-sleeptime>
>         <!-- evicts least frequently used items when pruning -->
>         <policy>com.whirlycott.cache.policy.LFUMaintenancePolicy</policy>
>         <maxsize>10000</maxsize>
>   </store>
>
> Regards,
> Eric Meyer
>


Mime
View raw message