Scarab commit: svn commit: r10287 - trunk/xdocs/howto/tuning-howto.xml

Author: jorgeuriarte
Date: 2006-09-08 14:13:49-0700
New Revision: 10287

Modified:
   trunk/xdocs/howto/tuning-howto.xml

Log:
Added info regarding cache-tuning.

Modified: trunk/xdocs/howto/tuning-howto.xml
Url: http://scarab.tigris.org/source/browse/scarab/trunk/xdocs/howto/tuning-howto.xml?view=diff&rev=10287&p1=trunk/xdocs/howto/tuning-howto.xml&p2=trunk/xdocs/howto/tuning-howto.xml&r1=10286&r2=10287
==============================================================================
--- trunk/xdocs/howto/tuning-howto.xml	(original)
+++ trunk/xdocs/howto/tuning-howto.xml	2006-09-08 14:13:49-0700
@@ -26,6 +26,25 @@
 auto-reload.  Set scarab.template.cache=TRUE to have caching turned on.
 </p>
 </subsection>
+
+<subsection name="Tuning the cache">
+<p>
+Scarab cache is central in the user experience of performance.
+You might want to take a look at the cache configuration file in:
+<pre>src/conf/classes/cache.ccf</pre>
+
+There you can tweak the number of objects (MaxObjects) of every type that will be kept in memory.
+<ul>
+<li>Module: If your instance is known to be limitated to a given number of modules, this should get a similar
+range.</li> 
+<li>ScarabUser: Must be an aproximation to the maximum concurrent number of users.</li>
+<li>Issue: A minimum equivalent to the ScarabUser's would be fine. Maybe something more, to keep a performance margin.</li>
+</ul>
+</p>
+<p>
+<b>Keep in mind: The greatest the size of the cache, the better performance AND the greater memory needs.</b>
+</p>
+</subsection>
 </section>
 
 </body>