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 jwall@google.com designates
 216.239.45.13 as permitted sender)
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to:
	content-type:x-gmailtapped-by:x-gmailtapped;
	b=T2rIXCeBjzd6Ed4vo9T4w+2iA3JEZMymIyGd0h+bcluBLYb43GNNeFCOmubnjBXxH
	LBuBChfz2e28sL1ppWRvA==
MIME-Version: 1.0
In-Reply-To: <9d5c45d10901071449m23f634c4v4efc6af6b8d8f3c9@mail.gmail.com>
References: <9d5c45d10901071449m23f634c4v4efc6af6b8d8f3c9@mail.gmail.com>
Date: Wed, 7 Jan 2009 17:07:26 -0600
Message-ID: <7c40ded80901071507h5562b403s10dd7992d8abf48d@mail.gmail.com>
Subject: Re: Slooooow views
From: Jeremy Wall <jwall@google.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001636c5c2f1604d80045fec960f

--001636c5c2f1604d80045fec960f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I'm not sure but from recent discussion on the list I think that reduces
happen at query time so complex reduces will slow down queries. Complex Maps
should only be an update time hit so those don't figure into a query when
the index is updated.

Maybe someone else could chime in on when you get the hit for reduction?

On Wed, Jan 7, 2009 at 4:49 PM, Chris Van Pelt <vanpelt@gmail.com> wrote:

> I'm pretty new to couch, and I'm wondering if there is a way to
> improve the performance of my views.  My views are very slow during
> generation, but also during simple queries.
>
> A request to one of my views after it is fully updated takes 2-4
> seconds.  The view is rather complex, using compound keys and an
> involved reduce step, but I assumed that didn't matter once the update
> step was complete.  I have 10000 documents in my DB.
>
> The update step, after adding 11 documents, takes 23 seconds.
>
> Because I have a web server talking directly to couch, I can't afford
> requests taking longer than a few seconds.  Ideally my requests would
> be in the tenths of seconds.  How do people deal with this in the real
> world?  I understand I can fire off view generation manually, but than
> all other requests hang while the view is being generated.
>
> I've also been looking for a way to edit my views without taking down
> my entire site for the 15 minutes it takes to regenerate the entire
> index.  It seems plausible to keep the old index around for queries
> while the new index is being created, no?
>
> Chris
>

--001636c5c2f1604d80045fec960f--