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 D4BC1D617 for ; Wed, 26 Sep 2012 02:03:22 +0000 (UTC) Received: (qmail 96618 invoked by uid 500); 26 Sep 2012 02:03:21 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 96583 invoked by uid 500); 26 Sep 2012 02:03:21 -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 96570 invoked by uid 99); 26 Sep 2012 02:03:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 02:03:21 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jens@couchbase.com designates 206.225.164.30 as permitted sender) Received: from [206.225.164.30] (HELO EXHUB020-3.exch020.serverdata.net) (206.225.164.30) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 02:03:16 +0000 Received: from EXVMBX020-1.exch020.serverdata.net ([169.254.4.4]) by EXHUB020-3.exch020.serverdata.net ([206.225.164.30]) with mapi; Tue, 25 Sep 2012 19:02:54 -0700 From: Jens Alfke To: "user@couchdb.apache.org" Date: Tue, 25 Sep 2012 19:02:52 -0700 Subject: Re: following fast doc updates Thread-Topic: following fast doc updates Thread-Index: Ac2biwpfA+hSfI4TTVq/+iRUMfm2fA== Message-ID: <0F98AFFD-AB92-4A30-82F2-A534A9F03901@couchbase.com> References: <6D6F51F2-9DE5-4CBB-9FB0-9511A863B972@apache.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org On Sep 25, 2012, at 5:59 PM, Mark Hahn wrote: > I am already using a scheme that requires me to store the latest revision > number for every doc in memory. You scheme would also require that and i= t > would cause extra reads. Correct me if I'm wrong. Sure, it requires extra reads if the _changes feed skipped a revision, but = it seems like the skipped revision and the read cancel out, so it=92s the s= ame amount of work as if you=92d gotten every revision. Is any of this worse than rewriting your app? :) =97Jens=