From dev-return-4604-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Fri Jun 12 22:04:33 2009 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 22995 invoked from network); 12 Jun 2009 22:04:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jun 2009 22:04:33 -0000 Received: (qmail 55060 invoked by uid 500); 12 Jun 2009 22:04:44 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 54968 invoked by uid 500); 12 Jun 2009 22:04:44 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 54958 invoked by uid 99); 12 Jun 2009 22:04:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jun 2009 22:04:44 +0000 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 jchris@gmail.com designates 209.85.218.218 as permitted sender) Received: from [209.85.218.218] (HELO mail-bw0-f218.google.com) (209.85.218.218) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jun 2009 22:04:34 +0000 Received: by bwz18 with SMTP id 18so3211852bwz.11 for ; Fri, 12 Jun 2009 15:04:13 -0700 (PDT) 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=ksrDxgKkZM3707MD3yz61TQfYDzJpZ3/q5CbFSS8Qeg=; b=ZSamqyfRyjRJL3u0HWGG3+j9Q2LkjM4B+RXqH0IMsvRUhPG6kmyCnVARgU0mJdY+R7 v6vKdZomJhSA7sA9B79yElHSHTLcvvO17KoUGOF3vBJShBLC/bp6XhC8Y5S4PJsf1+Q+ r6D6LquNVZIR2O9M0BCGsB4DRz4sMdaUa0qTA= 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=OGRxoyUfbEWchqsY+haLyRxH0Goxzfe5K0H7BlXQ4MY0tLj1r9N++njlz52YsixOvF y/w193BpgpPTEXznzGmViSK82F4zZBWKAyjPiAW0P0/XGfAv5vklEZGKxky0kpKSK6Ck oaK1TamZsOywa9XB50etd2b7FR8pWaBZjBcvU= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.204.119.129 with SMTP id z1mr4107083bkq.67.1244844252858; Fri, 12 Jun 2009 15:04:12 -0700 (PDT) In-Reply-To: <351BC7BB-BB6F-4333-A1E8-7A514121E1B1@googlemail.com> References: <351BC7BB-BB6F-4333-A1E8-7A514121E1B1@googlemail.com> Date: Fri, 12 Jun 2009 15:04:12 -0700 X-Google-Sender-Auth: 34aea657f5b1526b Message-ID: Subject: Re: Profiling views From: Chris Anderson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jun 10, 2009 at 9:34 AM, Simon Metson w= rote: > Hi All, > =A0 =A0 =A0 =A0I was wondering if there was any way of profiling views wi= thout using > a lot of log() statements. The application we are developing needs a lot = of > analytic information (who's querying what, how long a view takes to > generate, if a query comes in that doesn't map to a view etc.) and having > some decent timing reports on which views in a design document are taking= up > time would be really handy, so that we can set/manage update policy, cach= e > policies etc. In the current view architecture the views in a design doc will likely be hard to measure individually, as each doc is run through all views in a design doc in one go. Except for this detail, I support the idea of adding some metrics here. > Cheers > Simon > > PS. =A0My hope is that a lot (all?) of this analytic stuff can be done as= a > generic couchapp and made publicly available. Will try and keep people > posted as things start to materialise... > --=20 Chris Anderson http://jchrisa.net http://couch.io