cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-cocoon2/src/documentation/xdocs performancetips.xml
Date Mon, 12 Aug 2002 21:55:46 GMT
vgritsenko    2002/08/12 14:55:46

  Modified:    src/documentation/xdocs Tag: cocoon_2_0_3_branch
  new performance tip
  Revision  Changes    Path
  No                   revision
  No                   revision   +9 -2      xml-cocoon2/src/documentation/xdocs/performancetips.xml
  Index: performancetips.xml
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/performancetips.xml,v
  retrieving revision
  retrieving revision
  diff -u -r1.4.2.3 -r1.4.2.4
  --- performancetips.xml	7 Jul 2002 05:20:41 -0000
  +++ performancetips.xml	12 Aug 2002 21:55:46 -0000
  @@ -63,7 +63,6 @@
    <s1 title="Caching and Pooling">
        <li>Fine-tune the pool sizes for components in the files cocoon.xconf and
        sitemap.xmap. If the pools are too small for the load this will have a great
        impact on your performance. The goal is to achieve such a configuration that for 
  @@ -80,13 +79,21 @@
        caching appears to be very time consuming process.</li>
        <li>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 
  +     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.</li>
        <li>Watch the cachability in the log files, and make sure that things
         are being fed from the cache.</li>
        <li>Only use dynamic data when it is needed. Dynamic pages can't be
         cached 100%.</li>
  +     <li>Don't put Cocoon webapp too deep into directory structure. Cache
  +     keys contain absolute file names (or hash values of the absolute file
  +     names - in 2.0.X series), and the deeper cocoon is located in the
  +     filesystem, the longer keys are becoming. Obviously, longer keys will
  +     take more time to process them. In worst case scenario, slowdown up to
  +     10% could be achieved (unscientifical observations, do your own
  +     test).</li>

In case of troubles, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message