svn commit: r1392417 - /subversion/site/publish/docs/release-notes/1.7.html

[st...@apache.org]

Author: stefan2
Date: Mon Oct  1 16:07:01 2012
New Revision: 1392417

URL: http://svn.apache.org/viewvc?rev=1392417&view=rev
Log:
* site/publish/docs/release-notes/1.7.html
  (data-caches): make a clearer distinction between 1.7- and 1.6-style
   caching in the warning box

Modified:
    subversion/site/publish/docs/release-notes/1.7.html

Modified: subversion/site/publish/docs/release-notes/1.7.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.7.html?rev=1392417&r1=1392416&r2=1392417&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Mon Oct  1 16:07:01 2012
@@ -1256,16 +1256,17 @@ performance-optimal cache size.</p>
 	<p>If one of your repositories contains a folder with more than
 	10,000 entries (not counting files and folders in sub-trees),
 	you <b>must</b> increase the cache size.</p>
-    <p>Failure to do so may result in severe performance degradation
+   <p>Failure to do so may result in severe performance degradation
 	while working on that folder. 64 MByte will be enough to handle
 	25,000 entries per folder. For each time that number gets doubled,
 	the required cache size quadruples. I.e. 4 GByte will be good for
 	about 200,000 entries per folder.</p>
-    <p>Reverting to 1.6-style caching (see below) will reduce overall
+   <p>Reverting to 1.6-style caching (see below) will reduce overall
 	performance	and may cause your server process memory to grow
 	unpredictedly. However, it may help when the above limits are not
-	feasible. 64 MByte will then be good for 30,000 entries and
-	512 MByte for about 250,000.</p>
+	feasible. 64 MByte of dynamically allocated memory will then be
+	good for 30,000 entries and 512 MByte for about 250,000 when using
+	1.6-style caching.</p>
 </div>
 
 <p><tt>svnserve</tt> introduces a new optional <tt>--memory-cache-size</tt>