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 bitroot@gmail.com designates
 209.85.216.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=M6syi9ENjpNx0RIck0XTcxqllqO6ZDfn4kaRfdID3NGO0c2MBum9eQMtALXl2LXPwa
         YWAg3M0teHsximgC91yMgGITECTc+vszwU7NwfUBgYrpuG+k2t7bx90u6ZBGml3KQR9z
         Hp8Nr/m0AyCpPWE7jJhtJeib1eavfy7JGgvqM=
MIME-Version: 1.0
Sender: bitroot@gmail.com
In-Reply-To: <BANLkTintjxvH0rWY9bKVSht6p78nR55+GQ@mail.gmail.com>
References: <BANLkTik6aT0T9p4ja6bFtXfjA6E2w-ymUQ@mail.gmail.com>
	<BANLkTintjxvH0rWY9bKVSht6p78nR55+GQ@mail.gmail.com>
Date: Tue, 17 May 2011 22:22:33 +0100
Message-ID: <BANLkTimfUP4tkxJmznrmODURhyxeBsTY+w@mail.gmail.com>
Subject: Re: Bulk updates with an _update handler?
From: Joe Freeman <joe.freeman@bitroot.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 17 May 2011 21:12, Paul Davis <paul.joseph.davis@gmail.com> wrote:
> Fairly straight forward I suppose. Bigger question is whether its a good idea.

Why wouldn't it be a good idea?

Here's the problem I face:

The application I'm working on can potentially do lots of sequential
updates to separate documents (using requests to an _update handler).
When this happens there seems to be a big spike in the load on the
server. I'm presuming this is because the views get regenerated after
each of the updates (possibly because I'm using a _changes feed, and
re-requesting the view on each change).

I was under the impression this would be much more efficient if the
updates were being batched (so the view would only get regenerated
once after all the updates have been made?). Maybe I'm
misunderstanding the point of bulk updates, or just how views get
updated?