couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Couchdb Wiki] Update of "Performance" by RobertNewson
Date Mon, 21 Jan 2013 17:52:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Performance" page has been changed by RobertNewson:

remove block about -S, since it doesn't do that.

  The first option places an upper bound on the number of databases that can be open at one
time. CouchDB reference counts database accesses internally and will close idle databases
when it must. Sometimes it is necessary to keep more than the default open at once, such as
in deployments where many databases will be continuously replicating. The second option limits
how many client connections the HTTP server will service at a time. Again, heavy replication
scenarios are good candidates for increased {{{max_connections}}} since the replicator opens
several connections to the source database.
- == JavaScript View Server ==
- As of CouchDB 1.1.1+ the JavaScript view server that's included with CouchDB has an option
to tune the stack size for VM contexts. This option can be used if errors in the log indicate
that the stack quota has been exceeded. The value provided will be passed to [[JS_NewContext|]].
- {{{
- [query_servers]
- javascript = /usr/local/bin/couchjs -S 81920 /usr/local/share/couchdb/server/main.js
- }}}
- The example above shows a sample configuration which raises the stack size to 80kB from
the default of 8kB.
  == System Resource Limits ==
  === Erlang ===
  Even if you've increased the maximum connections CouchDB will allow, the Erlang runtime
system will not allow more than 1024 connections by default. Adding the following directive
to {{{(prefix)/etc/default/couchdb}}} (or equivalent) will increase this limit (in this case
to 4096):

View raw message