Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 95531 invoked from network); 4 Feb 2009 17:47:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2009 17:47:39 -0000 Received: (qmail 55879 invoked by uid 500); 4 Feb 2009 17:47:31 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 55852 invoked by uid 500); 4 Feb 2009 17:47:31 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 55828 invoked by uid 99); 4 Feb 2009 17:47:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 09:47:31 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rhettg@gmail.com designates 209.85.221.21 as permitted sender) Received: from [209.85.221.21] (HELO mail-qy0-f21.google.com) (209.85.221.21) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 17:47:24 +0000 Received: by qyk14 with SMTP id 14so3665402qyk.11 for ; Wed, 04 Feb 2009 09:46:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WYd54kDMbOpJqPLsnQCu5DUU3QCS59d97SmdPmjdyMA=; b=nSSXI1aPV16c9Q5Qy0bPiK63FSccixUToGVJ5D5P/I0cLnKPYYNCYU5nW9IRSqpX4+ agyrIvzGGV8fcrHhYZJhuFuEvFkeKi3jHD66iMcA03tpa1GzlDOdwfHZRc66wLtoBPk9 kSKY0cetEJtjNaVXlR+qZX3B5K9/X1mQvuZvE= 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=dyaL+FlJUng42BueZOl66jOabiFG5H1fJLYQQsSHZUmWAp7a7Pc+U7s96DDdk9tbNo 5KoPMfoodQSp3si1kVAvEPvn4MYFMqzO6hMFC70LBZbNwgK3OH3AupXRQufXfzaezupx XM19kCRIuosH1iP/1O2dEAcc0XeG9TyJXbTLA= MIME-Version: 1.0 Received: by 10.214.216.14 with SMTP id o14mr2774769qag.229.1233769618416; Wed, 04 Feb 2009 09:46:58 -0800 (PST) In-Reply-To: References: <41b0fe890902040013t3ed7844dn5e7485496626325c@mail.gmail.com> <00163646d64e341714046213e58e@google.com> Date: Wed, 4 Feb 2009 09:46:57 -0800 Message-ID: <41b0fe890902040946i68ae0ae5w7cd9b8c62485f9c3@mail.gmail.com> Subject: Re: Re: data loading From: Rhett Garber To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Feb 4, 2009 at 6:09 AM, Paul Davis wrote: > Third, if you have a good method for generating sorted document id's, > inserting sorted ID's into CouchDB *should* give you better write > performance. Chris Anderson had some luck with this from directly > within the Erlang VM. There's no reason it shouldn't apply to the HTTP > api as well but I haven't personally tested it just to make sure. It's advisable to create my own doc ids ? Why wouldn't they be sorted when couchdb creates them ? Or perhaps I should be asking, how are the doc ids in couchdb generated ? Rhett