Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.220.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=kHat7DfXnb+SkqIGdp5taH0eRuA+K/r+nMlnkC2xxEZOvdFpYjLn3AHkKXSoWiJ/Gf
         rtqbKWgrFt7Jwmw6CoLeE7bf9ams7c2LLM/m9jYMxYR57//D4mVp/UozvCWMUm+LF9XX
         QN17t0s6vtSOGJ4lcJFt/JNAeRdBmp/J4nKPc=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=KFhr=V086Xq0txt8=qM=v7W7pckJX2dd99hTX@mail.gmail.com>
References: <AANLkTikj02TLqL6tqfLAnsHTPr2bctYhYA5OkoMshNKX@mail.gmail.com>
 <AANLkTi=hO5GQCB80boA648_RyPMpcHtHO3y1PnuHw9Uq@mail.gmail.com>
 <AANLkTi=KFhr=V086Xq0txt8=qM=v7W7pckJX2dd99hTX@mail.gmail.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Mon, 21 Mar 2011 17:25:46 -0400
Message-ID: <AANLkTimDcL5q7OPUo4h3Zc8KoigYn70-xg6S7BSTH0s=@mail.gmail.com>
Subject: Re: blocking during view generation
To: Mark Hahn <mark@elleh.com>
Cc: user@couchdb.apache.org, Mark Hahn <mark@boutiquing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 21, 2011 at 4:49 PM, Mark Hahn <mark@elleh.com> wrote:
> What is the disadvantage to having a different design doc for each view?
>
> On Mon, Mar 21, 2011 at 11:05 AM, Paul Davis
> <paul.joseph.davis@gmail.com> wrote:
>> On Mon, Mar 21, 2011 at 1:24 PM, Mark Hahn <mark@boutiquing.com> wrote:
>>> I have noticed that all view queries are blocked for some time when I j=
ust
>>> change one view. =A0This seems like it is going to be a serious problem=
 when
>>> my db grows. =A0Is there someway to avoid this in production? =A0I've n=
ever seen
>>> mysql or any other db block for any reason.
>>>
>>
>> Also of note is that the updates are grouped at the _design/doc level,
>> so if you want to update some subset of views individually you just
>> need to split them amongst a set of _design/docs. There's also a
>> scheme that lets you create a temporary _design/doc that can be moved
>> over top of the existing version to have quickly updated views, but
>> this approach requires you to have the disk capacity to have both
>> versions built on disk simultaneously.
>>
>

Slightly more disk space used and longer total view build times due to
overhead of passing each doc to the view engine multiple times. Though
you can build multiple view groups in parallel if you have the CPU
resources.

Its hard to say exactly what the difference for each bit would be as
it depends directly on your specific data and usage patterns.