Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <1495659442.1250179574899.JavaMail.jira@brutus>
Date: Thu, 13 Aug 2009 09:06:14 -0700 (PDT)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Created: (COUCHDB-465) Produce sequential, but unique,
 document id's
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Produce sequential, but unique, document id's
---------------------------------------------

                 Key: COUCHDB-465
                 URL: https://issues.apache.org/jira/browse/COUCHDB-465
             Project: CouchDB
          Issue Type: Improvement
            Reporter: Robert Newson
         Attachments: sequence_id.patch

Currently, if the client does not specify an id (POST'ing a single document or using _bulk_docs) a random 16 byte value is created. This kind of key is particularly brutal on b+tree updates and the append-only nature of couchdb files.

Attached is a patch to change this to a two-part identifier. The first part is a random 12 byte value and the remainder is a counter. The random prefix 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 performance benefits.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.