subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From danie...@apache.org
Subject svn commit: r1598285 - /subversion/site/publish/docs/release-notes/1.9.html
Date Thu, 29 May 2014 12:59:35 GMT
Author: danielsh
Date: Thu May 29 12:59:34 2014
New Revision: 1598285

URL: http://svn.apache.org/r1598285
Log:
* docs/release-notes/1.9.html
  (#fsfs-improvements, #fsx): Add clarifications and one question.

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

Modified: subversion/site/publish/docs/release-notes/1.9.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1598285&r1=1598284&r2=1598285&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Thu May 29 12:59:34 2014
@@ -240,8 +240,11 @@ for erroneous settings lest they will be
      title="Link to this section">&para;</a>
 </h4>
 
-<p>The default repository format number is now 7.  In contrast to previous
-releases, this one is a major overhaul with the general goal of I/O reduction.
+<p>The default filesystem format is now a new format, numbered 7.
+(The command <tt>svnadmin info</tt> displays the filesystem format number
+of a repository.)
+In contrast to previous
+releases, format 7 is a major overhaul with the general goal of I/O reduction.
 Major changes include:
 </p>
 
@@ -292,7 +295,8 @@ however, it is strongly recommended to p
 with existing revisions.  Changing them is rarely necessary, but may result in
 slightly improved performance with your specific storage backend or when
 dealing with multi-TB repositories.  See the commentary in <tt>fsfs.conf</tt>
-for more information.
+for more information.  (You may have to create a new repository to see
+information about these settings in <tt>fsfs.conf</tt>.)
 
 <pre>
   [io]
@@ -311,10 +315,10 @@ for more information.
 
 <p>FSFS uses a combination of two methods to reduce on-disk data size.  First,
 we determine the changes (delta) against some previous version of the same file.
-This process can be controlled by fsfs.conf settings since 1.8.  The result
+This process can be controlled by <tt>fsfs.conf</tt> settings since 1.8.  The
result
 would then be compressed using ZIP/deflate.  That relatively costly operation
 limits commit speeds of large incompressible files.  You may now specify the
-compression level in fsfs.conf or disable the ZIP step entirely:
+compression level in <tt>fsfs.conf</tt> or disable compression entirely:
 </p>
 
 <pre>
@@ -337,9 +341,13 @@ speedup when using deltification vs. not
 <a href="#fsfs-caching">txdelta caches</a> when using directories
 deltification.</p>
 
-<p>If you don't want Subversion 1.9 to deltify properties and directories in
-older format repositories, modify or add the following settings in the
-repository’s fsfs.conf file:
+<p><span style="color: red"><i>### <b>TODO</b> "Don't disable"&mdash;why?
 What
+would happen if that setting were disabled?  Should the cache size be increased
+in the server configuration?</i></span></p>
+
+<p>To prevent Subversion 1.9 from deltifying properties and directories in
+older format repositories, set the following options in the
+repository’s <tt>fsfs.conf</tt> file:
 </p>
 
 <pre>
@@ -451,7 +459,8 @@ where FSX might be a viable option:</p>
 <p></p>
 
 <div class="notice">
-  <p>If you experiment with FSX, please let us know of your findings.  This
+  <p>If you experiment with FSX, please <a href="/mailing-lists">let us know</a>
+     of your findings.  This
      is your chance to get your use-case covered before storage format and
      principles of operation are set in stone.</p>
 </div>
@@ -474,9 +483,9 @@ dump and load</a> to upgrade an FSX repo
 
 <p>Dump and load is also the only upgrade path between FSFS and FSX.</p>
 
-<p>Finally, there is no guarantee that FSX will eventually be released at all.
-That means even if you find it useful in your specific environment, we might
-decide to remove FSX entirely from future releases.</p>
+<p>Finally, there is no guarantee that FSX will eventually be released at all;
+as an experimental backend, we make no promise that future releases will
+support reading or writing FSX repositories.</p>
 
 </div>  <!-- fsx-incompatibility -->
 



Mime
View raw message