Re: Advice/guideline on increasing shared_buffers and kernel parameters

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-admin(at)postgresql(dot)org>,<gnanam(at)zoniac(dot)com>
Subject: Re: Advice/guideline on increasing shared_buffers and kernel parameters
Date: 2012-05-08 14:38:35
Message-ID: 4FA8E99B0200002500047A16@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Gnanakumar" <gnanam(at)zoniac(dot)com> wrote:

> our web-based application has crossed more than 500 concurrent
> users. Hence we've already upgraded RAM and now we want to
> upgrade max connection parameter too. Yes, we're already using
> pgpool-II v3.1.1 for connection pooling.

The main point of using a connection pooler is to funnel a large
number of client connection into the pooler into a small number of
database connections. We get very good performance dealing with
thousands of concurrent users with a pool of 35 connections to the
database. We originally had a larger pool, but contention was
reducing performance, and we found that throughput and latency both
improved with a smaller pool of database connections.

If you want to handle more users than you can currently support, you
probably need to use fewer database connections.

-Kevin

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tim Bruce - Postgres 2012-05-08 14:57:18 Re: retaining useful information on my screen
Previous Message Fred Parkinson 2012-05-08 14:28:32 retaining useful information on my screen