Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 33769 invoked from network); 22 Jan 2009 19:22:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2009 19:22:51 -0000 Received: (qmail 72144 invoked by uid 500); 22 Jan 2009 19:22:49 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 72109 invoked by uid 500); 22 Jan 2009 19:22:49 -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 72098 invoked by uid 99); 22 Jan 2009 19:22:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2009 11:22:49 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 74.125.46.30 as permitted sender) Received: from [74.125.46.30] (HELO yw-out-2324.google.com) (74.125.46.30) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2009 19:22:40 +0000 Received: by yw-out-2324.google.com with SMTP id 3so1614355ywj.5 for ; Thu, 22 Jan 2009 11:22:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=GgIXh2p1V+TOOKuNTM8LScrFrb1pX+Y1Q4fHpzt+TCU=; b=iIG+A1hql317uGPPaJp1ptZGkTcbhyI1PgmOQ4fxcVthcP4k3IVhvt9AH1ulQRllRC 4SA100pNh0XAAusG20t8Q2/CsgDuhyV/NnF/sWPUWD/2jLkydE0vXeO/qXmcS50msMay J9K9Nyyc0FJpyJo7YcRn2RnGzTE374eBS7eoU= 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 :content-transfer-encoding; b=tz+FxX+J3QBP6sW7f78SxNYFlgD7yzUd12Vj9qscmdUfjOLon0hX9r1m/t3V4ipr0O B3ihCjY8Ra/5z2bMq9V11wle1+5MdvhjCzpla7mwjanmmcjfoLSVcRBbVuecaZ6V2LSw qKTzuBy9xR+iYRhG/LwE04BvvfnYk+ScGpdTs= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.64.213.20 with SMTP id l20mr787827qbg.133.1232652138528; Thu, 22 Jan 2009 11:22:18 -0800 (PST) In-Reply-To: <1232651911.13437.64.camel@chris-laptop> References: <1231947933.543.15.camel@chris-laptop> <13ae4dd50901140858x5e5c450uf14b67698756af3e@mail.gmail.com> <1232651911.13437.64.camel@chris-laptop> Date: Thu, 22 Jan 2009 11:22:18 -0800 X-Google-Sender-Auth: 7dfec6dffd108975 Message-ID: Subject: Re: Progress of view generation From: Chris Anderson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Jan 22, 2009 at 11:18 AM, Chris Wagner wrote: > FYI, this ended up taking a matter of days. I believe I was generating > two views at once, though. I'm uncertain whether a third view that I > have (in the same design document) was also being generated, however. > My view file is approximately 1.25 times the size of the database file. > all views in a design doc are generated in a single batch. This makes for less IO overhead to the Javascript process, as well as bulk operations to couchdb's on disk btrees. > Thanks for your help, Paul. :) > > > On Wed, 2009-01-14 at 16:58 +0000, Paul Carey wrote: >> Hi Chris >> >> > I have a database containing more than 11-million documents (87 GB). >> > >> > As can be expected, the view generation is taking quite a long time. >> > The problem is, though, that I have no idea how long it could take; I'm >> > not even sure whether it could be a matter of hours, days, weeks, ... >> >> At a guess, hours, probably quite a few. >> >> > So, I guess I am wondering if there's any way to gauge the progress of >> > the generation of these views -- or at least to be sure the views are >> > actually being generated and I'm not just watching the Futon >> > spinny-thing go on endlessly. >> >> There is indeed. Take a look at >> >> /usr/local/var/lib/couchdb/.my_design_doc.couch/Myview.view >> >> You should be able to see it growing while view generation is taking >> place. Given that you're emitting the doc as a value, and assuming >> your map function as is you stated e.g. no filtering is being >> performed, you can expect the size of the view file to be in the same >> ballpark as the size of you database. >> >> > That is, once the view has been generated once, can I be confident >> > that further generations (assuming I've only added a small number of >> > documents since the last generation) will be reasonably quick? >> >> Yes. >> >> Paul > > -- Chris Anderson http://jchris.mfdz.com