You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Ramkrishna Kulkarni <ra...@gmail.com> on 2013/10/04 03:38:06 UTC
Performance - Initiating over 100 simultaneous replications.
I'm initiating over 100 one shot replications to as many servers from a
central server. When I do this, central CouchDB slows down a lot (Requests
to DBs time out) even though enough system resources are available. I do
not see more than 600 connections (netstat -an | grep -i established | wc
-l) being opened at the time of replication. My config looks something like
this:
[couchdb]
max_dbs_open = 10000
[httpd]
max_connections = 10240
[replicator]
worker_processes = 30
http_connections = 30
/etc/security/limits.conf
* - nofile 65535
ulimit -n
65535
This is CouchDB 1.4.x on Ubuntu 12.04 32-bit, 8-cores, 6GB RAM.
I was hoping to see at least 3000 connections - 30 per replication. Is
there some other config I'm missing?
Thanks,
Ram
Re: Performance - Initiating over 100 simultaneous replications.
Posted by Ramkrishna Kulkarni <ra...@gmail.com>.
Hi,
I've set it to maximum - 65535. I tried opening 10K connections but all CPU
cores are peaking now. A large part of it I believe is due to the client
running on the same box. I still need to work on finding the right
combination of CouchDB and system settings to get the maximum throughput.
Ram.
On Sat, Oct 5, 2013 at 2:37 PM, Jens Rantil <je...@gmail.com> wrote:
> Ramkrishna,
>
> Just curious, what did you set the limits to for this to work?
>
> Cheers,
> Jens
>
>
> On Fri, Oct 4, 2013 at 2:42 PM, Ramkrishna Kulkarni <
> ramkrishna.kulkarni@gmail.com> wrote:
>
> > That worked! I can now see thousands of connections. Thanks a lot.
> >
> >
> > On Fri, Oct 4, 2013 at 4:01 PM, Robert Newson <rn...@apache.org>
> wrote:
> >
> > > One common gotcha with limits.conf is that couchdb su's to the couchdb
> > > user and /etc/pam.d/su in debian/ubuntu defaults to *not* respecting
> > > limits.conf, you need to enable it.
> > >
> > > B.
> > >
> > > On 4 Oct 2013, at 02:38, Ramkrishna Kulkarni <
> > > ramkrishna.kulkarni@gmail.com> wrote:
> > >
> > > > I'm initiating over 100 one shot replications to as many servers
> from a
> > > > central server. When I do this, central CouchDB slows down a lot
> > > (Requests
> > > > to DBs time out) even though enough system resources are available. I
> > do
> > > > not see more than 600 connections (netstat -an | grep -i established
> |
> > wc
> > > > -l) being opened at the time of replication. My config looks
> something
> > > like
> > > > this:
> > > >
> > > > [couchdb]
> > > > max_dbs_open = 10000
> > > >
> > > > [httpd]
> > > > max_connections = 10240
> > > >
> > > > [replicator]
> > > > worker_processes = 30
> > > > http_connections = 30
> > > >
> > > > /etc/security/limits.conf
> > > > * - nofile 65535
> > > >
> > > > ulimit -n
> > > > 65535
> > > >
> > > > This is CouchDB 1.4.x on Ubuntu 12.04 32-bit, 8-cores, 6GB RAM.
> > > >
> > > > I was hoping to see at least 3000 connections - 30 per replication.
> Is
> > > > there some other config I'm missing?
> > > >
> > > > Thanks,
> > > > Ram
> > >
> > >
> >
>
Re: Performance - Initiating over 100 simultaneous replications.
Posted by Jens Rantil <je...@gmail.com>.
Ramkrishna,
Just curious, what did you set the limits to for this to work?
Cheers,
Jens
On Fri, Oct 4, 2013 at 2:42 PM, Ramkrishna Kulkarni <
ramkrishna.kulkarni@gmail.com> wrote:
> That worked! I can now see thousands of connections. Thanks a lot.
>
>
> On Fri, Oct 4, 2013 at 4:01 PM, Robert Newson <rn...@apache.org> wrote:
>
> > One common gotcha with limits.conf is that couchdb su's to the couchdb
> > user and /etc/pam.d/su in debian/ubuntu defaults to *not* respecting
> > limits.conf, you need to enable it.
> >
> > B.
> >
> > On 4 Oct 2013, at 02:38, Ramkrishna Kulkarni <
> > ramkrishna.kulkarni@gmail.com> wrote:
> >
> > > I'm initiating over 100 one shot replications to as many servers from a
> > > central server. When I do this, central CouchDB slows down a lot
> > (Requests
> > > to DBs time out) even though enough system resources are available. I
> do
> > > not see more than 600 connections (netstat -an | grep -i established |
> wc
> > > -l) being opened at the time of replication. My config looks something
> > like
> > > this:
> > >
> > > [couchdb]
> > > max_dbs_open = 10000
> > >
> > > [httpd]
> > > max_connections = 10240
> > >
> > > [replicator]
> > > worker_processes = 30
> > > http_connections = 30
> > >
> > > /etc/security/limits.conf
> > > * - nofile 65535
> > >
> > > ulimit -n
> > > 65535
> > >
> > > This is CouchDB 1.4.x on Ubuntu 12.04 32-bit, 8-cores, 6GB RAM.
> > >
> > > I was hoping to see at least 3000 connections - 30 per replication. Is
> > > there some other config I'm missing?
> > >
> > > Thanks,
> > > Ram
> >
> >
>
Re: Performance - Initiating over 100 simultaneous replications.
Posted by Ramkrishna Kulkarni <ra...@gmail.com>.
That worked! I can now see thousands of connections. Thanks a lot.
On Fri, Oct 4, 2013 at 4:01 PM, Robert Newson <rn...@apache.org> wrote:
> One common gotcha with limits.conf is that couchdb su's to the couchdb
> user and /etc/pam.d/su in debian/ubuntu defaults to *not* respecting
> limits.conf, you need to enable it.
>
> B.
>
> On 4 Oct 2013, at 02:38, Ramkrishna Kulkarni <
> ramkrishna.kulkarni@gmail.com> wrote:
>
> > I'm initiating over 100 one shot replications to as many servers from a
> > central server. When I do this, central CouchDB slows down a lot
> (Requests
> > to DBs time out) even though enough system resources are available. I do
> > not see more than 600 connections (netstat -an | grep -i established | wc
> > -l) being opened at the time of replication. My config looks something
> like
> > this:
> >
> > [couchdb]
> > max_dbs_open = 10000
> >
> > [httpd]
> > max_connections = 10240
> >
> > [replicator]
> > worker_processes = 30
> > http_connections = 30
> >
> > /etc/security/limits.conf
> > * - nofile 65535
> >
> > ulimit -n
> > 65535
> >
> > This is CouchDB 1.4.x on Ubuntu 12.04 32-bit, 8-cores, 6GB RAM.
> >
> > I was hoping to see at least 3000 connections - 30 per replication. Is
> > there some other config I'm missing?
> >
> > Thanks,
> > Ram
>
>
Re: Performance - Initiating over 100 simultaneous replications.
Posted by Robert Newson <rn...@apache.org>.
One common gotcha with limits.conf is that couchdb su's to the couchdb user and /etc/pam.d/su in debian/ubuntu defaults to *not* respecting limits.conf, you need to enable it.
B.
On 4 Oct 2013, at 02:38, Ramkrishna Kulkarni <ra...@gmail.com> wrote:
> I'm initiating over 100 one shot replications to as many servers from a
> central server. When I do this, central CouchDB slows down a lot (Requests
> to DBs time out) even though enough system resources are available. I do
> not see more than 600 connections (netstat -an | grep -i established | wc
> -l) being opened at the time of replication. My config looks something like
> this:
>
> [couchdb]
> max_dbs_open = 10000
>
> [httpd]
> max_connections = 10240
>
> [replicator]
> worker_processes = 30
> http_connections = 30
>
> /etc/security/limits.conf
> * - nofile 65535
>
> ulimit -n
> 65535
>
> This is CouchDB 1.4.x on Ubuntu 12.04 32-bit, 8-cores, 6GB RAM.
>
> I was hoping to see at least 3000 connections - 30 per replication. Is
> there some other config I'm missing?
>
> Thanks,
> Ram