Index: www/faq.html
===================================================================
--- www/faq.html	(revision 14779)
+++ www/faq.html	(working copy)
@@ -212,7 +212,7 @@
 <h4>Developer questions:</h4>
 <ul>
 <li><a href="#ramdisk-tests">How do I run the regression tests in a
-    ram disk?</a></li>
+    RAM disk?</a></li>
 </ul>
 
 <h4>References:</h4>
@@ -2770,14 +2770,33 @@
 
 <h3><a name="ramdisk-tests" title="#ramdisk-tests"
     >How do I run the regression tests in a
-    ram disk?</a></h3>
+    RAM disk?</a></h3>
 
-<p>
-See
-<a href="http://svn.haxx.se/dev/archive-2003-02/0068.shtml"
->http://svn.haxx.se/dev/archive-2003-02/0068.shtml</a>.
+<p>Test execution can be dramatically sped up by keeping Subversion
+test data on a RAM disk.  On a Linux system, add lines like the
+following in your /etc/fstab file:
+
+<blockquote><code>
+<div>tmpfs  /home/brane/svn/obj-sh/subversion/tests  tmpfs  defaults,user,noauto,exec,size=64m</div>
+<div>tmpfs  /home/brane/svn/obj-st/subversion/tests  tmpfs  defaults,user,noauto,exec,size=64m</div>
+</code></blockquote>
+
+The minimum required size for testing ramdisk is approximately 700MB.
+However, flagging your test targets for cleanup dramatically reduces
+the space requirements (as shown in the example configuration above),
+and thus your memory usage.  Cleanup means more I/O, but since test
+data is in-memory, there will be no performance degradation.  Example:
+
+<blockquote><code>
+make check CLEANUP=true
+</code></blockquote>
+
 </p>
 
+<p>See <a href="http://svn.haxx.se/dev/archive-2003-02/0068.shtml"
+>http://svn.haxx.se/dev/archive-2003-02/0068.shtml</a> for the
+original authoritative discussion on use of RAM disks.</p>
+
 <![CDATA[=========================================================]]>
 
 
Index: tools/test-scripts/svntest/svntest-run.sh
===================================================================
--- tools/test-scripts/svntest/svntest-run.sh	(revision 14779)
+++ tools/test-scripts/svntest/svntest-run.sh	(working copy)
@@ -74,6 +74,10 @@
 if test "xyes" = "x$RAMDISK";
 then
     reinitialize_ramdisk
+
+    # Flag the tests to cleanup to avoid requiring hundreds of MBs of
+    # memory.
+    CHECK_ARGS="$CHECK_ARGS CLEANUP=1"
 fi
 
 # Prepare the server
Index: tools/test-scripts/svntest/README
===================================================================
--- tools/test-scripts/svntest/README	(revision 14779)
+++ tools/test-scripts/svntest/README	(working copy)
@@ -1,6 +1,14 @@
-Using the svntest scripts                                 -*- Text -*-
-=========================
+svntest scripts                                           -*- Text -*-
+===============
 
+This set of scripts is designed to wrap execution of all of
+Subversion's Makefile test targets (e.g. "check", "davcheck",
+"svncheck", etc.).
+
+
+Usage
+=====
+
 1) Read the INSTALL (http://svn.collab.net/repos/svn/trunk/INSTALL)
    file, especially the sections about bootstrapping from a tarball
    and getting the latest APR-0.9, APR-UTIL-0.9 and httpd-2.0 sources.
@@ -123,16 +131,23 @@
 5) Make sure your environment (e.g., LD_LIBRARY_PATH) is set correctly
    to find Berkeley DB, etc.
 
-6) If you like run test against ramdisk (subversion test data will be held on ramdisk)
-   then you should have something like that in your /etc/fstab (in Linux system):
-   tmpfs           /home/brane/svn/obj-sh/subversion/tests tmpfs defaults,user,noauto,exec,size=700m
-   tmpfs           /home/brane/svn/obj-st/subversion/tests tmpfs defaults,user,noauto,exec,size=700m
+6) Test execution can be dramatically sped up by keeping Subversion
+   test data on a RAM disk.  On a Linux system, add lines like the
+   following in your /etc/fstab file:
 
-   The minimum required size for ramdisk is appr. 570 MB at the moment.  
-   You should also set RAMDISK=yes, and check mount_ramdisk and umount_ramdisk 
-   in the svntest-config.sh file if your system is not GNU/Linux.
-   See http://subversion.tigris.org/project_faq.html#ramdisk-tests for 
-   further information.
+   tmpfs  /home/brane/svn/obj-sh/subversion/tests  tmpfs  defaults,user,noauto,exec,size=64m
+   tmpfs  /home/brane/svn/obj-st/subversion/tests  tmpfs  defaults,user,noauto,exec,size=64m
+
+   The minimum required size for testing RAM disk is actually many
+   times greater than shown above.  However, svntest will
+   automatically flag your test targets for cleanup when using a
+   ramdisk, which dramatically reduces the space requirement.
+
+   To enable RAM disk usage by svntest, set RAMDISK=yes, and check
+   mount_ramdisk and umount_ramdisk in the svntest-config.sh file if
+   your system is not GNU/Linux.  See
+   http://subversion.tigris.org/faq.html#ramdisk-tests for further
+   information.
    
 7) Run svntest.sh to get the latest versions of ARP, APR-UTIL, HTTPPD and
    Subversion, build and test all the configurations.