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 FilipeManana: http://wiki.apache.org/couchdb/Performance?action=diff&rev1=13&rev2=14 If you have a fast I/O system then you can also use concurrency - have multiple requests/responses at the same time. This mitigates the latency involved in assembling JSON, doing the networking and decoding JSON. - As of CouchDB 1.1.0, users often report lower write performance of documents compared to older releases. The main reason is that this release ships with a more recent version of the HTTP server library Mochiweb, which by default sets the TCP socket option ''SO_NODELAY'' to false. This means that small data sent to the TCP socket, like the reply to a document write request (or reading a very small document), will not be sent immediately to the network - TCP will buffer it for a while hoping that it will be asked to send more data through the same socket data and then send all the data at once for increased performance. This TCP buffering behaviour can be disabled via the .ini configuration for all sockets. Example: + As of CouchDB 1.1.0, users often report lower write performance of documents compared to older releases. The main reason is that this release ships with a more recent version of the HTTP server library Mochiweb, which by default sets the TCP socket option ''SO_NODELAY'' to false. This means that small data sent to the TCP socket, like the reply to a document write request (or reading a very small document), will not be sent immediately to the network - TCP will buffer it for a while hoping that it will be asked to send more data through the same socket and then send all the data at once for increased performance. This TCP buffering behaviour can be disabled via the .ini configuration for all sockets. Example: {{{ [httpd]
