You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by vg...@apache.org on 2002/08/12 23:55:46 UTC

cvs commit: xml-cocoon2/src/documentation/xdocs performancetips.xml

vgritsenko    2002/08/12 14:55:46

  Modified:    src/documentation/xdocs performancetips.xml
  Log:
  new performance tip
  
  Revision  Changes    Path
  1.8       +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 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- performancetips.xml	7 Jul 2002 05:20:09 -0000	1.7
  +++ performancetips.xml	12 Aug 2002 21:55:46 -0000	1.8
  @@ -63,7 +63,6 @@
    
    <s1 title="Caching and Pooling">
      <ul>
  -      
        <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>
      </ul>
    </s1>
    
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org