Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5010F9C5E for ; Mon, 2 Apr 2012 07:29:45 +0000 (UTC) Received: (qmail 95516 invoked by uid 500); 2 Apr 2012 07:29:44 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94936 invoked by uid 500); 2 Apr 2012 07:29:36 -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 94901 invoked by uid 99); 2 Apr 2012 07:29:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 07:29:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,TO_NO_BRKTS_PCNT X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.212.52] (HELO mail-vb0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 07:29:30 +0000 Received: by vbzb23 with SMTP id b23so2119114vbz.11 for ; Mon, 02 Apr 2012 00:29:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=hxVjU1y8PzmMIv71HfipbU2GFKsr4DaArUlz7p1kyuY=; b=gChBwhrY0mtFjUmCYGL+8v9KH6ojKo2AMLOxBTsqKkX/E8bvTC9cNpE9A+QQ4VEGeD NOxfQX0mgITl63GDUUt1r17OQWf/2NUWRC5ydqkB5mLlskiip6mSZ8TI+GHo9txPWJBl HhsUODtqonyF6eKvRTUvQoYxRM09z2EM9HYe3P0qPbmqYD/Tv10pJglI9gEF1H8y6gC6 fUzzc9NnPKunJfNZxGpVMJ0Sk0z5yQmqEuDqgz6UBdANP/mCfkdQwN3DxR/C6730EBDx 1rT8k1rzgSM2lEdRJJ1A074nsHi/zpOAaMzCxg5kARhGbx1TULiPKeywzVgSjm9nPbTT BDVw== Received: by 10.52.90.20 with SMTP id bs20mr2811876vdb.98.1333351749237; Mon, 02 Apr 2012 00:29:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.160.234 with HTTP; Mon, 2 Apr 2012 00:28:49 -0700 (PDT) X-Originating-IP: [68.5.117.177] In-Reply-To: References: From: Mark Hahn Date: Mon, 2 Apr 2012 00:28:49 -0700 Message-ID: Subject: Re: how to debug a single PUT that is very slow? To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf307f35125fba3504bcad258a X-Gm-Message-State: ALoCoQnwE7gak/fVmFfNLUpAQW+IvCjTJlbTGZrA0V2RAJCYcgVE3XTdCOscPTT79ty3Tf08EZuy X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f35125fba3504bcad258a Content-Type: text/plain; charset=ISO-8859-1 > Do you have a validate_doc_update function in any design documents in that database? No, just an update handler and a few filters. I use the update handler a lot, almost every PUT. I rarely PUT an entire doc except when creating a new one, as in this situation. Interesting. I'm having a problem while lots of update handlers are running. I wonder if this is a significant clue. On Mon, Apr 2, 2012 at 12:02 AM, Jason Smith wrote: > Hi, Mark. Do you have a validate_doc_update function in any design > documents in that database? > > Thanks. > > On Mon, Apr 2, 2012 at 1:41 PM, Mark Hahn wrote: > > I'm having a problem in a particular situation where a specific put of a > > new document is taking 10 to 20 seconds. The db is not very loaded down. > > There are 5 to 25 writes/sec and about 200 reads per second. I have a > db > > watcher that is invoked on every change. > > > > Looking at the log timestamps, the PUT for the new document doesn't even > > register as an [info] line until ten seconds after my app sent the http > > request. The log just shows normal read and writes during that 10 > seconds. > > No view is being rebuilt nor is there a compaction happening. > > > > I can repeat this any time I want by uploading 18 files from my browser, > > where each of the 18 triggers an invocation of imagemagick thumbnail > > conversion and then adding that thumbnail as an attachment to each of 18 > > docs. The attachments are only about 20 kbytes each. The doc that is > > trying to be created is unrelated to any of those 18. The problem just > > happens when I try to create the doc at the same time. > > > > The cpu is not loaded. Node and the db are only consuming about 15% each > > of the cpu during the episode. > > > > Any idea what could cause this? What can I do to track the problem down? > > > > -- > Iris Couch > --20cf307f35125fba3504bcad258a--