Re: Merging parallel-put to /trunk
From: Greg Stein <gstein_at_gmail.com>
Date: Sat, 6 Feb 2016 07:09:00 -0600
On Fri, Feb 5, 2016 at 3:27 AM, Evgeny Kotkov <evgeny.kotkov_at_visualsvn.com>
> (1) Why do we start with adding a quite complex FS feature, given that we
Please do not deny a new feature, on the *supposition* that problems *may*
Let's move forward, and not hold back on a mere thought of other problems.
FWIW, serf can manage multiple connections, all runnings PUTs to the
Our commit code flow may need work to support it, but that does NOT detract
> (Can we actually do it? What can be parallelized while keeping the
Oh, give me a break. "not officially supported" ... This is a public list.
Both of those components have H/2 support now.
(2) Is making parallel PUTs the proper way to speed up commits?
Absolutely. Typically, the PUT is a delta against a prior revision, it may
I seem to recall an inspection of our server time, that showed MD5 handling
> As far as I know, squashing everything into a single POST would make
> So, are we sure that we need to implement it this way?
Yes. We've been wanting parallel PUTs for years. The backend has denied us.
This is an archived mail posted to the Subversion Dev mailing list.