Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Handling small inserts from many connections.
From: "Michaeldba@sqlexec.com" <Michaeldba@sqlexec.com>
In-Reply-To: 
 <CAOR=d=2PzwsUFh8qZoPH7OuAz2hMmOpNPtJikm9zsNofM4xCXQ@mail.gmail.com>
Date: Mon, 4 Sep 2017 18:06:24 -0400
Cc: =?utf-8?B?7Jqw7ISx66+8?= <dntjdals0513@gmail.com>,
 "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1282F40-A721-4A0B-BCFB-ED314771EF6E@sqlexec.com>
References: 
 <CABdtbz0LZOEXYAh6f=PpLvF57jk2B4UOH2y5ETtHpv7ibu_17A@mail.gmail.com>
 <CAOR=d=2PzwsUFh8qZoPH7OuAz2hMmOpNPtJikm9zsNofM4xCXQ@mail.gmail.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Jumping on Scott's observation, assuming you really do have a lot of active=
 connections (idle ones usually are not a problem) a general rule of thumb =
for not overloading your system is keep your active connections less than (=
2-3) * (number so cpus).

Sent from my iPad

> On Sep 4, 2017, at 2:15 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
>=20
>> On Mon, Sep 4, 2017 at 2:14 AM, =EC=9A=B0=EC=84=B1=EB=AF=BC <dntjdals051=
3@gmail.com> wrote:
>> Hi team,
>>=20
>> I'm trying to configure postgres and pgbouncer to handle many inserts fr=
om
>> many connections.
>>=20
>> Here's some details about what i want to achieve :
>>=20
>>  We have more than 3000 client connections, and my server program forks
>> backend process for each client connections.
>=20
> This is a terrible configuration for any kind of performance. Under
> load all 3,000 connections can quickly swamp your server resulting in
> it slowing to a crawl.
>=20
> Get a connection pooler involved. I suggest pgbouncer unless you have
> very odd pooling needs. It's easy, small, and fast. Funnel those 3,000
> connections down to <100 if you can. It will make a huge difference in
> performance and reliability.
>=20
>> System information :
>>  PGBouncer 1.7.2.
>>  PostgreSQL 9.6.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7
>> 20120313 (Red Hat 4.4.7-18), 64-bit on CentOS release 6.9 (Final).
>>  Kernel version 2.6.32-696.10.1.el6.x86_64
>>  Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz processor.
>>  32GB ECC/REG-Buffered RAM.
>>  128GB Samsung 840 evo SSD.
>=20
> If it's still slow after connection pooling is setup, then look at
> throwing more SSDs at the problem. If you're using a HW RAID
> controller, turn off caching with SSDs unless you can prove it's
> faster with it. It almost never is.
>=20
>=20
> --=20
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance


--=20
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance