Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 63980 invoked from network); 3 Nov 2008 09:27:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Nov 2008 09:27:23 -0000 Received: (qmail 23153 invoked by uid 500); 3 Nov 2008 09:27:28 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 23115 invoked by uid 500); 3 Nov 2008 09:27:28 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 23104 invoked by uid 99); 3 Nov 2008 09:27:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2008 01:27:28 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.52.237.208] (HELO x8.develooper.com) (216.52.237.208) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2008 09:26:12 +0000 Received: (qmail 27191 invoked from network); 3 Nov 2008 09:26:52 -0000 Received: from gw.develooper.com (HELO embla.bn.dev) (ask@mail.dev@64.81.84.140) by smtp.develooper.com with (AES128-SHA encrypted) SMTP; 3 Nov 2008 09:26:52 -0000 Message-Id: <46302F0F-7FF1-475B-B341-E7699295D915@apache.org> From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= To: couchdb-user@incubator.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: Largest CouchDB dbs? Date: Mon, 3 Nov 2008 01:26:50 -0800 References: <8C1EE3D1-D62F-4C6A-A859-196297E09C3D@apache.org> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org On Nov 2, 2008, at 21:19, Paul Davis wrote: > View updates are admittedly slower than we'd like. There's planned > work on making this sort of thing parallelized to automagically fill > out multi-node clusters. Last I remember this is a 'probably 1.0' > feature though. I wonder if some of the slowness is from running it through JS? Perl has an extremely fast JSON parser (JSON::XS), would there be any potential optimization in using an alternate view language like that - or is most of the time spent elsewhere? I don't expect more than a few tens of thousands of new documents a day though, so other than on index changes this isn't such a big deal. - ask