subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1349726 - /subversion/site/publish/docs/release-notes/1.8.html
Date Wed, 13 Jun 2012 10:20:31 GMT
Author: stsp
Date: Wed Jun 13 10:20:30 2012
New Revision: 1349726

* publish/docs/release-notes/1.8.html: Some more relevant notes on neon's
  removal, partly lifted from 1.7 release notes.


Modified: subversion/site/publish/docs/release-notes/1.8.html
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Wed Jun 13 10:20:30 2012
@@ -102,14 +102,13 @@ and what impact these changes may have.<
     <th>Minimum Repository</th>
-    <td><a href="#httpv2">XXX(1.7) HTTPv2</a></td>
-    <td>1.7</td>
-    <td>1.7</td>
+    <td><a href="#neon-deleted">ra_neon</a> removed</td>
+    <td>1.8</td>
-    <td>Permutations of older client/server combinations will continue to
-      function at the pre-1.7 feature level. Server-side configuration
-      changes might be required for optimal performance with clients that
-      use <a href="#serf">serf</a>.</td></tr>
+    <td>any</td>
+    <td><a href="#neon-deleted">Server-side configuration changes</a>
+      might be required for optimal performance with 1.8 clients which
+      access the repository via HTTP.</td></tr>
      <td colspan="5"><sup>1</sup>Reminder: when using the <tt>file://</tt>
        repository access method, the Subversion program is both the client
@@ -195,6 +194,27 @@ the ra_serf repository access method for
 the development burden of maintaining multiple HTTP client interfaces (and sets
 of bugs!) ra_serf is now the only HTTP client provider for Subversion.</p>
+<div class="notice">
+<p>Note that 
+<a href=""
+>server-side configuration changes</a> might be required to avoid
+performance regressions for serf clients in some setups.</p>
+<p>The <strong>MaxKeepAliveRequests</strong> option in <tt>httpd.conf</tt>
+needs to be increased from 100 (the default) to <b>at least</b> 1000
+(there is no reason why it could not be 10000).
+This will improve performance by allowing serf clients to use fewer
+TCP connections to the server.
+Clients using neon will also work fine with this configuration.</p>
+<p>Because serf clients issue a larger number of HTTP GET requests
+than neon clients it is possible that serf clients cause quicker
+growth of httpd server logs than neon clients do. As of 1.7.3, 
+the httpd error logs may also grow more rapidly with serf clients
+than with neon clients; see
+<a href=";view=rev"
 </div>  <!-- neon-deleted -->
 <div class="h3" id="compat-misc">

View raw message