Index: publish/docs/release-notes/1.8.html =================================================================== --- publish/docs/release-notes/1.8.html (revision 1494710) +++ publish/docs/release-notes/1.8.html (working copy) @@ -389,7 +389,7 @@ HTTP client interfaces (and sets of bugs!) serf is client provider for Subversion.
Note that +
Note that server-side configuration changes might be required to avoid performance regressions for serf clients in some setups.
@@ -402,22 +402,120 @@ Clients using neon will also work fine with this cThis affects any server version, when accessed with a 1.8 -client.
+The svn 1.8 client with serf defaults to skelta mode for update +operations (checkout, update, merge and export) instead of the bulk update mode +used by previous versions. Skelta mode was introduced in Subversion 1.6.0 and +improved in 1.8.0. It uses one HTTP request and response per resource that needs +to be fetched from the server, whereas bulk update mode fetches all resources in +one massive reponse.
-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 +
The main benefit of skelta mode is that it allows a correctly set up Apache +server or intermediate proxy server to cache mod_dav_svn’s responses to +handle later requests from the cache. This results in improved performance of +svn client operations and reduced CPU usage on the server side. It also allows +a more detailed audit of clients accessing resources in a Subversion +repository.
+ +Skelta mode has some disadvantages:
+This release introduces two options to control if the svn client will use +skelta or bulk update mode.
++
Set SVNAllowBulkUpdates to Prefer if your +server configuration does not allow an intermediate caching server - on your +side or on the client's side - to successfully cache server responses.
+Table explaining the mode used between each combination of svn client and +server version and relevant configuration directives:
+ ++ | 1.8 Server with SVNAllowBulkUpdates: |
+ 1.7 and older Server with SVNAllowBulkUpdates: |
+ |||
---|---|---|---|---|---|
Subversion Client | +Off | +On* | +Prefer | +Off | +On* | +
1.8, http-bulk-updates: auto* | +Skelta mode | +Skelta mode | +Bulk mode | +Skelta mode | +Bulk mode | +
1.8, http-bulk-updates: yes | +Skelta mode | +Bulk mode | +Bulk mode | +Skelta mode | +Bulk mode | +
1.8, http-bulk-updates: no | +Skelta mode | +Skelta mode | +Skelta mode | +Skelta mode | +Skelta mode | +
1.7 and older with neon* | +Skelta mode | +Bulk mode | +Bulk mode | +Skelta mode | +Bulk mode | +
1.7 and older with serf | +Skelta mode | +Skelta mode | +Skelta mode | +Skelta mode | +Skelta mode | +
*Default configuration
+