couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-1282) Allow special value 0 for os_process_limit
Date Wed, 14 Sep 2011 22:52:09 GMT


Randall Leeds updated COUCHDB-1282:

    Attachment: 0001-Smart-os_proc_limit-default-COUCHDB-1282.patch

    Smart os_proc_limit default (COUCHDB-1282)
    With this change, default.ini specifies the value 0 for os_process_limit. This
    value tells couch to use the number of logical processors reported as the
    default limit. The aim is to make couch better optimized for the deployment by
    default, transparently scaling the query server count to maximize performance
    and minimize scheduler overhead.

> Allow special value 0 for os_process_limit
> ------------------------------------------
>                 Key: COUCHDB-1282
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Randall Leeds
>            Assignee: Randall Leeds
>            Priority: Trivial
>         Attachments: 0001-Smart-os_proc_limit-default-COUCHDB-1282.patch
> It's unlikely to be beneficial to run more os processes than there are logical processors
in a system. It creates extra scheduling overhead if they are all in use. Currently default.ini
specifies 25, though the code specifies 10 if the option is missing, and I expect both are
too high for many real world deployments.
> I propose the value 0 be used in default.ini and that it take special meaning: use the
number of logical processors erlang detects.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message