Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <1283627726.1236095936072.JavaMail.jira@brutus>
Date: Tue, 3 Mar 2009 07:58:56 -0800 (PST)
From: "Chris Anderson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-277) Improve the OS process handling to
 have pool semantics.
In-Reply-To: <1636817159.1236045116404.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678353#action_12678353 ] 

Chris Anderson commented on COUCHDB-277:
----------------------------------------

There are a couple of notes here:

One is that couch_query_servers (which is in charge of baby-sitting views, lists and shows) already manages a pool of processes to avoid opening and closing them.

The second is that the main.js protocol could be enhanced so that the reduce, show, etc funs can be named (by md5?) so that they don't have to be resent for each request.

> Improve the OS process handling to have pool semantics.
> -------------------------------------------------------
>
>                 Key: COUCHDB-277
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-277
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Paul Joseph Davis
>
> Just got reminded that I need to add pool semantics to OS processes. Now that we're using JS processes for more and more things other than Map/Reduce this will be especially important.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.