From user-return-22079-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Mon Sep 10 21:06:54 2012 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 41196D2CD for ; Mon, 10 Sep 2012 21:06:54 +0000 (UTC) Received: (qmail 1362 invoked by uid 500); 10 Sep 2012 21:06:51 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 1322 invoked by uid 500); 10 Sep 2012 21:06:50 -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 1307 invoked by uid 99); 10 Sep 2012 21:06:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 21:06:50 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andrew.melo@gmail.com designates 209.85.210.52 as permitted sender) Received: from [209.85.210.52] (HELO mail-pz0-f52.google.com) (209.85.210.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 21:06:43 +0000 Received: by dakf10 with SMTP id f10so1817231dak.11 for ; Mon, 10 Sep 2012 14:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LJg2Mtx2DPgRoQnwYRsjRmLLpTXusYw62UzqdUm/0Qs=; b=rFtS6WkKheJ/lp5Yh1L+Bc45vXojLGx4fPM6ZiYDPQSLM8/BpctNsgmAR/yQBBZLrn G1wZbikU/QM5Hk19GxdzwFbMqU+xSZ6pN2nlD3rMA1uJLUpB++1lD5f9uiDDrfalxUxM aRGoJXhZHbz9kwdUQiAyyTlPY6yqUDHG+peI0ZsLSjSu/oM0N6sg9mj9nf+qAq8AyBIK 0XfEhzvUD47qbkHue3BGROIt7oVuGhoLNvHq0yjCAUR73sjQ4yh6RSHa8TsIYuaUT1/Q LLQayYOR7Et4vc3jyEU5yiLIx/tLYlhoUotU2ms8rJHQ0eBMwiX7lL+fDG6EbtBbtSDv NFJg== MIME-Version: 1.0 Received: by 10.66.88.1 with SMTP id bc1mr23294449pab.18.1347311181480; Mon, 10 Sep 2012 14:06:21 -0700 (PDT) Received: by 10.66.220.161 with HTTP; Mon, 10 Sep 2012 14:06:21 -0700 (PDT) Date: Mon, 10 Sep 2012 16:06:21 -0500 Message-ID: Subject: View generation parallelism From: Andrew Melo To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=f46d042e00c15fc5b704c95f5408 --f46d042e00c15fc5b704c95f5408 Content-Type: text/plain; charset=UTF-8 Hello all, Can someone remind me (I'm having trouble finding it) the way couch decides to split up work to external couchjs processes? If I have a couch server with several databases and several design documents, each with several view and _update handlers, how many ways will couch partition the task of generating views and executing _update handlers? Does each database/view document get one process, or is the logic more complex? Along with that do views and _update handlers run in the same couch process? Thanks in advance, Andrew -- -- Andrew Melo --f46d042e00c15fc5b704c95f5408--