Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA2A9D3C2 for ; Fri, 18 Jan 2013 03:37:57 +0000 (UTC) Received: (qmail 54629 invoked by uid 500); 18 Jan 2013 03:37:56 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 54590 invoked by uid 500); 18 Jan 2013 03:37:55 -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 54562 invoked by uid 99); 18 Jan 2013 03:37:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 03:37:54 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.212.173] (HELO mail-wi0-f173.google.com) (209.85.212.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 03:37:46 +0000 Received: by mail-wi0-f173.google.com with SMTP id hn17so4970174wib.6 for ; Thu, 17 Jan 2013 19:37:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-originating-ip:in-reply-to:references :from:date:message-id:subject:to:content-type:x-gm-message-state; bh=JM9df/gJl1FKAd3Pe5P8MJc0LbbvKp9H/rfJ86PzaZA=; b=V7tqi106jK6bvoN28AuYwH/4Dg8mcvO1/yoo8ovqoktit8dWslAjVTO9WDOL8ON1F7 t2Sekdpvs3+JDCYHe87Hd2Eci6vjEW6FgMNWTwI0bYxM9zLWS37cPhg+GDNKcbplHJIf n6t3LPHBdTGlQl8+jY8WIk0bk+/MboTHb6XMfUPA2hyar0KiviKfjuMxPeNtcDooC5yr ZuPc5vPvEeAs+svY2GNpYiF1DlhaybXwfhG2WLi6QMD/i3LNSnHDqi9el0Nxtp+ajink TnOf94o9wvrIbIJl7bii7WpSX68ldx4CxU+ADc2HeTgbc3Zx2FHLmf9LAW8wwiqwaLvl y25A== X-Received: by 10.180.95.169 with SMTP id dl9mr1267624wib.20.1358480244839; Thu, 17 Jan 2013 19:37:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.217.47.67 with HTTP; Thu, 17 Jan 2013 19:37:04 -0800 (PST) X-Originating-IP: [68.5.117.177] In-Reply-To: <692973B6DC2848C3A5BFD268DC73158A@gmail.com> References: <692973B6DC2848C3A5BFD268DC73158A@gmail.com> From: Mark Hahn Date: Thu, 17 Jan 2013 19:37:04 -0800 Message-ID: Subject: Re: general question about couch performance To: user Content-Type: multipart/alternative; boundary=f46d041827006d948604d387d4cc X-Gm-Message-State: ALoCoQnH1QKDKnh7mktObH+fWI3xH98eONipoLssiEYIizzziI+6NDaaEj+fSbWJ+b5DiUkOXMn5 X-Virus-Checked: Checked by ClamAV on apache.org --f46d041827006d948604d387d4cc Content-Type: text/plain; charset=ISO-8859-1 Thanks. > Now for IDs I thought this API [1] was for retrieving sequential UUIDs I just read your reference [1]. I was surprised to read that what is labelled "sequential" is only partially sequential. The prefix is random. So it is a UUID after all, not a simple sequence . So using them on multiple doc generating servers is not a problem. I'll have to consider this. Now my only problem is that currently my app takes advantage of the utc_random algorithm. I use the id to keep docs sequenced in time and I even pull the creation time out of the ID. In retrospect that was pretty stupid. --f46d041827006d948604d387d4cc--