Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of robert.newson@gmail.com
 designates 209.85.218.211 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=QeVtRH8ObhAVZZkt2etV2yGQaVKkjY038vrqsgxUU/3BKT59ViLaP0ttAeli083OkB
         5Vp9xtGqm286G3yIZUjd6K2/3MhFDpiimTw6bTYGb/jK6zzTa0ee0WBDUXz235lm5NBY
         qey4jftdOxN/6zaZT0L9+WxYGsayoT6c6JUT8=
MIME-Version: 1.0
In-Reply-To: <763245036.1252513317515.JavaMail.jira@brutus>
References: <1495659442.1250179574899.JavaMail.jira@brutus>
	 <763245036.1252513317515.JavaMail.jira@brutus>
Date: Wed, 9 Sep 2009 17:30:02 +0100
Message-ID: <46aeb24f0909090930y6406ca8j5bc0ee4ccaaad260@mail.gmail.com>
Subject: Re: [jira] Updated: (COUCHDB-465) Produce sequential, but unique,
	document id's
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

Since the default is staying with random, I see no reason not to
commit it today :)

B.

On Wed, Sep 9, 2009 at 5:21 PM, Adam Kocoloski (JIRA)<jira@apache.org> wrot=
e:
>
> =A0 =A0 [ https://issues.apache.org/jira/browse/COUCHDB-465?page=3Dcom.at=
lassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Adam Kocoloski updated COUCHDB-465:
> -----------------------------------
>
> =A0 =A0Fix Version/s: 0.11
>
> Yes, this is going into 0.11. =A0It looks like things have stabilized; is=
 there any reason not to commit it today?
>
>> Produce sequential, but unique, document id's
>> ---------------------------------------------
>>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: COUCHDB-465
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/jira/brow=
se/COUCHDB-465
>> =A0 =A0 =A0 =A0 =A0 =A0 Project: CouchDB
>> =A0 =A0 =A0 =A0 =A0Issue Type: Improvement
>> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Robert Newson
>> =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 0.11
>>
>> =A0 =A0 =A0 =A0 Attachments: 041-uuid-gen-seq.ini, 041-uuid-gen-utc.ini,=
 041-uuid-gen.t, couch_uuids.patch, uuid_generator.patch
>>
>>
>> Currently, if the client does not specify an id (POST'ing a single docum=
ent or using _bulk_docs) a random 16 byte value is created. This kind of ke=
y is particularly brutal on b+tree updates and the append-only nature of co=
uchdb files.
>> Attached is a patch to change this to a two-part identifier. The first p=
art is a random 12 byte value and the remainder is a counter. The random pr=
efix is rerandomized when the counter reaches its maximum. The rollover in =
the patch is at 16 million but can obviously be changed. The upshot is that=
 the b+tree is updated in a better fashion, which should lead to performanc=
e benefits.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>