Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of robert.newson@gmail.com
 designates 209.85.220.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=bQNG5S90XOKWHBVuP2gwWq5F4FzY7k4YyC1xmmj41HAJ2+4T/3ouPLCdN5hCRULciZ
         oFVpR38MlX8fxGEYjOoS4/eo7KpvArVCvj7USn2bOODh6R/UIlsxZHI7cTCsjc8Vvcjf
         xfoirnttaK6fbKJisegmuc8vjQ51ZGn97TZig=
MIME-Version: 1.0
In-Reply-To: <5ECBD9A9-1D4E-4841-8C54-4351A565DAEC@apache.org>
References: <8CD75D2A-F8EB-451C-B10A-899461BE2CEF@apache.org>
	 <5ECBD9A9-1D4E-4841-8C54-4351A565DAEC@apache.org>
Date: Tue, 25 Aug 2009 16:24:32 +0100
Message-ID: <46aeb24f0908250824g3851de94g8b36bec22dbf40e7@mail.gmail.com>
Subject: Re: replication patches and new _ensure_full_commit feature
From: Robert Newson <robert.newson@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1

The improvements are huge. There are other fixes since this thread
started that finally allowed my stress test to pass, I think they all
should go into 0.10.

B.

On Tue, Aug 25, 2009 at 3:13 PM, Damien Katz<damien@apache.org> wrote:
> +1
>
> On Aug 24, 2009, at 11:26 PM, Adam Kocoloski wrote:
>
>> Hi all, I committed a good bit of replication-related code today and
>> wanted to check with the list regarding the 0.10 branch. =A0Here's what =
I
>> changed ..
>>
>> one flat-out bugfix,
>> r807308, r807354: more precise and accurate calculation of replication
>> progress
>>
>> one new feature that could be classified as a bugfix depending on your
>> point-of-view,
>> r807342, r807345: follow 302 redirects during replication
>>
>> and two significant performance improvements (thanks rnewson for all the
>> stress testing):
>> r807320, r807360: checkpoint at most once per 5 seconds
>> r807208, r807459, r807461: minimize the number of full commit operations
>>
>> There's another new feature hiding in that last set of commits, namely t=
he
>> ability to do a restricted full commit
>>
>> POST /db/_ensure_full_commit?seq=3DN
>>
>> which guarantees that everything up to and including update_seq N will b=
e
>> synced to disk. =A0This is a weaker guarantee than a vanilla
>> _ensure_full_commit, and as a result it can be much faster in certain
>> situations (e.g. replication from a server experiencing a heavy batch=3D=
ok
>> write load).
>>
>> I'd like to merge all of these into the 0.10 branch if that abides by ou=
r
>> release policies. Best,
>>
>> Adam
>
>