Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 1547 invoked from network); 7 Jan 2009 22:50:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jan 2009 22:50:19 -0000 Received: (qmail 38343 invoked by uid 500); 7 Jan 2009 22:50:13 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 38305 invoked by uid 500); 7 Jan 2009 22:50:13 -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 38294 invoked by uid 99); 7 Jan 2009 22:50:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2009 14:50:13 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vanpelt@gmail.com designates 209.85.198.237 as permitted sender) Received: from [209.85.198.237] (HELO rv-out-0506.google.com) (209.85.198.237) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2009 22:50:06 +0000 Received: by rv-out-0506.google.com with SMTP id g37so8397167rvb.35 for ; Wed, 07 Jan 2009 14:49:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=i1agGEV63EI/R1diCi90uP35ebIdJg/AFRrBf9SZ8VY=; b=kD9rYtD28nen24lg4VSwXPBtxritl/6XO1DdUkM08dVhtTTDXFAwpd/0FKNyZE9d5o 6jVS5x7s9XiKrY0UxTNxO/YCB9YwviJU2NfnEFXoP3SzQBOO+pmAJWRM2iYRWw3OMKCo V/wYBUtwfLi6a0rjO4Mvq5XSKaeNWLwRhObYU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=jNyKRpMxMlIwjYz5D4UGaXNsoOODViaJyhamOH+ZfWZr6xfTOZ5dldtLNSNjNOcD6Y Y3aOeZFi0SqPmavpz9SGo7eL9vK4pL282YbzfjOK2n4ofiMGIlqbui80A3vNjYZyTSPV /4ereJEommIJ5aHvh7wRWNRqu+NJnjipTWdP8= Received: by 10.141.141.3 with SMTP id t3mr10846282rvn.104.1231368586301; Wed, 07 Jan 2009 14:49:46 -0800 (PST) Received: by 10.140.134.2 with HTTP; Wed, 7 Jan 2009 14:49:46 -0800 (PST) Message-ID: <9d5c45d10901071449m23f634c4v4efc6af6b8d8f3c9@mail.gmail.com> Date: Wed, 7 Jan 2009 14:49:46 -0800 From: "Chris Van Pelt" To: user@couchdb.apache.org Subject: Slooooow views MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org 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