couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <>
Subject Re: general question about couch performance
Date Thu, 17 Jan 2013 12:27:40 GMT
Hi Mark!

Have you tried to tweak httpd options? In local.ini there is their definition:

; Options for the MochiWeb HTTP server.
;server_options = [{backlog, 128}, {acceptor_pool_size, 16}]
; For more socket options, consult Erlang's module 'inet' man page.
;socket_options = [{recbuf, 262144}, {sndbuf, 262144}, {nodelay, true}]

For example, disabling Nagle algorithm through {nodelay,true} socket
option may dramatically change rps value[1].

That is about network operations. For disk one there is
delayed_commits option, but it requires to suffer data durability for
some speed and actually it's not recommended to keep them him with
true value.


On Thu, Jan 17, 2013 at 12:17 AM, Mark Hahn <> wrote:
> My couchdb is seeing a typical request rate of about 100/sec when it is
> maxed out.  This is typically 10 reads/write.  This is disappointing.  I
> was hoping to 3 to 5 ms per op, not 10 ms.  What performance numbers are
> others seeing?
> I have 35 views with only 50 to 100 entries per view.  My db is less than a
> gigabyte with a few thousand active docs.
> I'm running on a medium ec2 instance with ephemeral disk.  I assume I am IO
> bound as the cpu is not maxing out.
> How much worse would this get if the db also had to handle replication
> between multiple servers?

View raw message