> I think that local commits are usually fast enough. But committing over
> a high-latency network, e.g., with a transatlantic RTT of 150ms, can be
> painfully slow — see below.
Poor network connections are of course a very important concern, likely even
more important than some additional seco
Greg Stein writes:
>> Results without and with the patch are:
>>
>> Importing 1 files, 150 ms RTT1887.582 s → 46.363 s(40.7x
>> faster)
>
> Is that normal-svn vs single-POST-svn?
>
> Or is that parallel-PUT-svn vs single-POST-svn?
That is normal-svn vs single-POST-svn.
Regards,
E
Evgeny Kotkov writes:
> How faster is a commit going to be with parallel PUTs? Would that be
> at least twice faster?
If I take a 250MB file containing random data and commit over http to
localhost it takes 16s on my machine. The first 8s is the client
running at 100% CPU the second 8s
On Thu, Feb 11, 2016 at 6:40 AM, Evgeny Kotkov
wrote:
>...
> >> As far as I know, squashing everything into a single POST would make
> >> the commit up to 10-20 times faster, depending on the amount of
> changes.
> >
> > Pfft.
>
> I attached a dirty patch that does that. The aim is to me
Greg Stein writes:
> Oh, give me a break. "not officially supported" ... This is a public list.
> I'll be nice.
>
> Both of those components have H/2 support now.
I might have misinterpreted the warning banner in httpd documentation [1]
saying that mod_http2 is experimental (or maybe this statem
On Fri, Feb 5, 2016 at 3:27 AM, Evgeny Kotkov
wrote:
>...
> (1) Why do we start with adding a quite complex FS feature, given that we
> don't know what kind of problems are associated with implementing this
> in ra_serf?
>
Please do not deny a new feature, on the *supposition* that pr
Stefan Fuhrmann writes:
> The extra temporary space is not a concern: Your server would run out of
> disk space just one equally large revision earlier than it does today.
I wouldn't say it is not a concern at all — e.g., in the situation where a
user cannot possibly commit a 4 GB file just beca
On 29.01.2016 22:35, Evgeny Kotkov wrote:
Stefan Fuhrmann writes:
This branch adds support for HTTP2-style transactions to all backends.
The feature is opt-in and supported in all 3 FS implementations.
I'd like to merge this to /trunk next weekend, so that e.g. Bert can
continue the work on t
Stefan Fuhrmann writes:
> This branch adds support for HTTP2-style transactions to all backends.
> The feature is opt-in and supported in all 3 FS implementations.
>
> I'd like to merge this to /trunk next weekend, so that e.g. Bert can
> continue the work on the network layer. Because it is opt-
On 24.01.2016 00:53, Daniel Shahaf wrote:
Stefan Fuhrmann wrote on Sat, Jan 23, 2016 at 13:53:08 +0100:
Hi there,
This branch adds support for HTTP2-style transactions
to all backends. The feature is opt-in and supported
in all 3 FS implementations.
I'd like to merge this to /trunk next weeken
Stefan Fuhrmann wrote on Sat, Jan 23, 2016 at 13:53:08 +0100:
> Hi there,
>
> This branch adds support for HTTP2-style transactions
> to all backends. The feature is opt-in and supported
> in all 3 FS implementations.
>
> I'd like to merge this to /trunk next weekend, so that
> e.g. Bert can cont
Hi there,
This branch adds support for HTTP2-style transactions
to all backends. The feature is opt-in and supported
in all 3 FS implementations.
I'd like to merge this to /trunk next weekend, so that
e.g. Bert can continue the work on the network layer.
Because it is opt-in, removing the featur
12 matches
Mail list logo
