Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 88796 invoked from network); 21 Jan 2009 13:19:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2009 13:19:45 -0000 Received: (qmail 56887 invoked by uid 500); 21 Jan 2009 13:19:42 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 56860 invoked by uid 500); 21 Jan 2009 13:19:42 -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 56849 invoked by uid 99); 21 Jan 2009 13:19:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 05:19:42 -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 dundeemt@gmail.com designates 209.85.198.226 as permitted sender) Received: from [209.85.198.226] (HELO rv-out-0506.google.com) (209.85.198.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 13:19:35 +0000 Received: by rv-out-0506.google.com with SMTP id g37so3628740rvb.35 for ; Wed, 21 Jan 2009 05:19:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oPopDxp2YwgRPN+8p0ZPYdVcpC0xbZKEnY3Nao+Nxso=; b=bsRZQYmQmdLfJFY3rnlORiqA9PlIWZAi0TgATpXK5xl/uERg7X2fFVRBOdUvH9sBE6 gkI3T1tGt9bplOFxYuBaiPDBkN4IdvkTVdpCWKT2cL/env7q63LGNk/8BWF0ItHyPwpf BbFX6MUhG3fepqw6tGXvw0bWdNVLufDX3dlyk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=lialXs1xGVBPpWNArpBUsRxw8qe/vHjxF+a835ysGIqMO/YJtxmRTMzUOxZrPefWnQ jVr3K9Ow8xoJbWlGQT3ummX3Zv18rItVA6RR3lXLpqXO4BPmRljfpDB2jNazIFnn9tgt lXxRBetA4yxxZnO33ybIyDTHNFWLfKpj3/b/0= MIME-Version: 1.0 Sender: dundeemt@gmail.com Received: by 10.141.209.6 with SMTP id l6mr2805856rvq.192.1232543955048; Wed, 21 Jan 2009 05:19:15 -0800 (PST) Date: Wed, 21 Jan 2009 07:19:15 -0600 X-Google-Sender-Auth: e744dd4e06a7f0e8 Message-ID: <5aaed53f0901210519v1d836352pb3af4a53e9232e43@mail.gmail.com> Subject: timing views From: "Jeff Hinrichs - DM&T" To: couchdb-user Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Is there currently a way to get time information for a map and/or reduce functions? If not intrinsically via couch, what method has anyone used? I realize that optimizations has not been a consideration for couch during it's alpha nor beta, but I'm looking for information on user/developer written code, i.e. map and reduce functions. I am trying to understand what penalty is imposed for using an alternative scripting language such as python or ruby as compared to using javascript. Also, what effect map/reduce user code optimizations have on initial view creation and on-going incremental runs. If there isn't a "good" way currently, that is an acceptable answer and I am definitely not asking to add something to the pre 1.0 feature list if it is not there. The current things on that list are all more important than the ability to instrument user code. Regards, Jeff