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 2A8874EF9 for ; Fri, 10 Jun 2011 13:19:54 +0000 (UTC) Received: (qmail 33059 invoked by uid 500); 10 Jun 2011 13:19:52 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 33016 invoked by uid 500); 10 Jun 2011 13:19:52 -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 33008 invoked by uid 99); 10 Jun 2011 13:19:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jun 2011 13:19:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sean.copenhaver@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jun 2011 13:19:47 +0000 Received: by vws16 with SMTP id 16so3158874vws.11 for ; Fri, 10 Jun 2011 06:19:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=5YUsEBjUGVbzohkFEa1XpJkCdJnOFWzPnVmLU5pJpHM=; b=FppZRcGuJJbIvchAnATv81dVefBS8iimq3uKFiYcLTcIQaV5kZIEgQ/7yzdu0/p6P7 qnpLtzw4IQiGqr0/co3+JhCxgtoF68qdg9xxv1MaNjAz1wp9Q0TueDzvFC3lygOFslSi PujKuQpS2L0tcuC5kDLUsp6xE2OJb4z8h6OnU= 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; b=wZHSpHLNW7dMgSia3TKN1KWKxlpXJujCxsTjCiOYaWIRk3ozjK3iEI8B2c+a1CGkyR hryt7wUEOH6DoQlxcsURl0bIwPNGtvrffiYQYqTR6c96UC4YouTjn1sJ3gJrCkAEKt6j CewwGtXuKe3IU2NUiayUWYlEYNXH7Vlc6YMlk= MIME-Version: 1.0 Received: by 10.52.175.197 with SMTP id cc5mr2937655vdc.287.1307711966234; Fri, 10 Jun 2011 06:19:26 -0700 (PDT) Received: by 10.52.185.167 with HTTP; Fri, 10 Jun 2011 06:19:26 -0700 (PDT) In-Reply-To: <87tybxsu90.wl%omarshall@facilityone.com> References: <64497E8E-7AEA-4E30-A44E-5AD285887150@challet.eu> <87tybxsu90.wl%omarshall@facilityone.com> Date: Fri, 10 Jun 2011 09:19:26 -0400 Message-ID: Subject: Re: One view per "query"? From: Sean Copenhaver To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec51a7d4237464704a55b6b95 --bcaec51a7d4237464704a55b6b95 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable You can also hit the views with a 'stale=3Dupdate_after' if on 1.1. On Fri, Jun 10, 2011 at 9:15 AM, Owen Marshall w= rote: > At Fri, 10 Jun 2011 12:05:20 +0200, > Daniele Testa wrote: > > > Another question I have is what benefit do I get when putting several > > views in one design document? > > Views within the same design document are indexed together, saving space > and speeding up view updates. > > > As I understood, this just causes problems like that all views needs > > to update, thus locking all the views in the design document. > > I was also concerned about this at first, but in my experience, CouchDB > updates views *very* quickly. My application's write rate is significantl= y > less than CouchDB's update rate. > > If your application doesn't behave like that, you can always: > > * query with stale=3Dok as appropriate > * hit the views more often, reducing latency > > -- > Owen Marshall > FacilityONE > http://www.facilityone.com | (502) 805-2126 > > --=20 =93The limits of language are the limits of one's world. =93 -Ludwig von Wittgenstein --bcaec51a7d4237464704a55b6b95--