Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of omarshall@facilityone.com
 designates 216.135.43.146 as permitted sender)
Date: Fri, 10 Jun 2011 09:15:07 -0400
Message-ID: <87tybxsu90.wl%omarshall@facilityone.com>
From: Owen Marshall <omarshall@facilityone.com>
To: user@couchdb.apache.org
Subject: Re: One view per "query"?
In-Reply-To: <BANLkTikHEejT0H8asSS0kgSbM9bDcy9MVg@mail.gmail.com>
References: <BANLkTikXKOBg7V-M8BFEJbdiyHAPdruD_Q@mail.gmail.com>
	<64497E8E-7AEA-4E30-A44E-5AD285887150@challet.eu>
	<BANLkTikHEejT0H8asSS0kgSbM9bDcy9MVg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.6 (Marutamachi) APEL/10.8 Emacs/24.0.50 (x86_64-unknown-linux-gnu)
 MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII

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 significantly less than CouchDB's update rate.

If your application doesn't behave like that, you can always:

* query with stale=ok as appropriate
* hit the views more often, reducing latency

-- 
Owen Marshall
FacilityONE
http://www.facilityone.com | (502) 805-2126