On Thu, Sep 20, 2012 at 1:41 PM, <stefan2_at_apache.org> wrote:
> Author: stefan2
> Date: Thu Sep 20 11:41:25 2012
> New Revision: 1387981
> URL: http://svn.apache.org/viewvc?rev=1387981&view=rev
> On 10Gb branch, add a README.
> * BRANCH-README: new file
> Added: subversion/branches/10Gb/BRANCH-README
> URL: http://svn.apache.org/viewvc/subversion/branches/10Gb/BRANCH-README?rev=1387981&view=auto
> --- subversion/branches/10Gb/BRANCH-README (added)
> +++ subversion/branches/10Gb/BRANCH-README Thu Sep 20 11:41:25 2012
> @@ -0,0 +1,15 @@
> +This branch will receive a number of patches that boost
> +svn:// single-threaded throughput from about 5Gb/s to
> +10Gb/s for typical source code, i.e. becomes capable of
> +saturating a 10Gb connection.
> +Bottlenecks to address:
> +* frequent cancellation checks (intense OS interaction)
> +* in-memory copies (membuffer cache -> empty deltification
> + -> output buffer -> network stack)
> +* various CPU-heavy tasks
> +The patches have been written quite some time ago and I
> +want them off my disk. OTOH, release 1.8 shall not be
As a mod_dav_svn user, I'm wondering:
- How much of your current set of patches will also benefit
(indirectly perhaps) mod_dav_svn?
- For the things that only help svnserve, how much of those could be
implemented for mod_dav_svn as well (practically and/or theoretically
-- perhaps some of those would need a totally different approach, but
maybe the principle is valid for mod_dav_svn as well)?
Or is mod_dav_svn just not able to get a higher throughput because of
other reasons (protocol overhead, other bottlenecks, ...)?
Received on 2012-09-21 21:44:58 CEST