Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[ADMIN] High-end PG database configuration help

1 view
Skip to first unread message

Gupta, Amar Nath

unread,
Jul 20, 2016, 6:47:19 AM7/20/16
to

Hello,

 

I am working to configure high end PostgreSQL database, and need some help.

 

Please can you suggest me best and optimal configuration for “postgresql.conf” I should use.

 

DB server details:

·         PostgreSQL Version: 9.5.3

·         Disc: RAID 10 (1 TB)

·         DB Size: 250GB

·         RAM: 256GB

·         CPU(s): 48

·         Max Connection: 2000

·         OS: CentOS release 6.6 (Final)

 

Many thanks in advanced.

 

Best Regards,

Amar

 

Confidentiality Notice

This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure.

If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (937-226-7724) or reply to this e-mail and delete all copies of this message.

Gupta, Amar Nath

unread,
Jul 21, 2016, 5:03:52 PM7/21/16
to

I would appreciate, if anyone provide me some guidance

 

Best,

Amar

Scott Whitney

unread,
Jul 21, 2016, 5:16:48 PM7/21/16
to
I would be happy to consult on this.


Your requirements are vague. 


Journyx, Inc.
7600 Burnet Road #300
Austin, TX 78757
www.journyx.com

Do you receive our promotional emails? You can subscribe or unsubscribe to those emails at http://go.journyx.com/emailPreference/e/4932/714/ 

David G. Johnston

unread,
Jul 21, 2016, 5:23:07 PM7/21/16
to
On Thu, Jul 21, 2016 at 4:58 PM, Gupta, Amar Nath <ang...@corbus.com> wrote:

I would appreciate, if anyone provide me some guidance



​Configuration is not strictly a function of hardware...

Having a working feedback loop is more important that getting the initial values perfect.​

There are many email threads, blog posts, books, and open source software tools that can aid in this exercise.  I'd suggest searching for some of those while waiting for people to donate their time here.  If you get impatient while waiting I'd recommend you consider professional services companies or individuals.

Dave
 

Scott Marlowe

unread,
Jul 21, 2016, 5:37:43 PM7/21/16
to
On Wed, Jul 20, 2016 at 4:45 AM, Gupta, Amar Nath <ang...@corbus.com> wrote:
> Hello,
>
> I am working to configure high end PostgreSQL database, and need some help.
>
> Please can you suggest me best and optimal configuration for
> “postgresql.conf” I should use.
>
> DB server details:
>
> · PostgreSQL Version: 9.5.3
>
> · Disc: RAID 10 (1 TB)
>
> · DB Size: 250GB
>
> · RAM: 256GB
>
> · CPU(s): 48
>
> · Max Connection: 2000
>
> · OS: CentOS release 6.6 (Final)

A few quick pointers.

1: describe what your workload looks like. How you configure a server
can vary quite a bit depending on what it's doing.
2: If that RAID-10 is spinning disks pull them, throw them in the
trash, and buy some SSDs. A pair of 800GB Intels costs $1000 total,
and you don't even need the RAID controller with them to be fast.
3: Pick a distro that can run the 3.11 or higher kernels. IO is MUCH
MUCH faster in the later model kernels than in the older 2.6.32 kernel
Centos 6 uses. Ubuntu 12.04 can easily run a 3.11 or 3.13 kernel from
the standard repos. Not sure about Centos 6, but I'm pretty sure it
takes more than a simple rpm command to get a later model kernel into
it.
4: Look into connection pooling. NO database is gonna be fast if it
has 2,000 connections all active at once. I've got 80 core machines
with 3 super fast 1TB SSD cards in them that would fall over under the
load of 2,000 active connections.
5: Don't go crazy on shared_buffers. A few gig is usually plenty, let
the OS do the majority of the heavy lifting when it comes to caching
data.

There's more to discuss, but we don't know what you're trying to do
yet, so I'll wait to hear back from you (Please keep it on the list so
others can benefit)


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

Gupta, Amar Nath

unread,
Jul 22, 2016, 3:59:31 AM7/22/16
to
Many thanks for your reply Scott,

Point#1: we have two DB servers (web app and reporting database). Web app does simple read and insert query + some complex queries. And reporting DB is used for heave queries
Point#2: will do in next update ;)
Point#3: I'll check for that.
Point#4: Agreed, opening 2000 connection is not a good idea. Somehow my application is setup in this way I cannot use pgpool, but working on it in long term.
Point#5: I have setup 32GB for that.

Server current configuration is:
max_connections = 2000
shared_buffers = 32GB
work_mem = 128MB
synchronous_commit = off
effective_cache_size = 192GB

rest settings are on default

Regards,
Amar

-----Original Message-----
From: Scott Marlowe [mailto:scott....@gmail.com]
Sent: 21 July 2016 22:36
To: Gupta, Amar Nath <ang...@corbus.com>
Cc: pgsql...@postgresql.org
Subject: Re: [ADMIN] High-end PG database configuration help

Confidentiality Notice

This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure.

If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (937-226-7724) or reply to this e-mail and delete all copies of this message.

--

Scott Marlowe

unread,
Jul 22, 2016, 12:14:59 PM7/22/16
to
On Fri, Jul 22, 2016 at 1:57 AM, Gupta, Amar Nath <ang...@corbus.com> wrote:
> Many thanks for your reply Scott,
>
> Point#1: we have two DB servers (web app and reporting database). Web app does simple read and insert query + some complex queries. And reporting DB is used for heave queries
> Point#2: will do in next update ;)
> Point#3: I'll check for that.
> Point#4: Agreed, opening 2000 connection is not a good idea. Somehow my application is setup in this way I cannot use pgpool, but working on it in long term.
> Point#5: I have setup 32GB for that.
>
> Server current configuration is:
> max_connections = 2000
> shared_buffers = 32GB
> work_mem = 128MB
> synchronous_commit = off
> effective_cache_size = 192GB
>
> rest settings are on default

Which of your two dbs has 2,000 connections and needs tuning, the
reporting db or the web db?

Two points:

1: Rarely if ever is 32GB needed for shared_buffers. There's a cost to
have more shared_buffers and it's pretty rare that anything over 1 or
2GB is needed. If you have a performance test showing you need more
than a few G then yes, go for it.

2: You've got to get max_connections down to something reasonable.
Look at pgbouncer. It's super easy to setup and will allow you to drop
the # connections to 100 or so even for busy dbs with lots of users
etc.

Gilberto Castillo

unread,
Jul 22, 2016, 12:43:02 PM7/22/16
to
Maybe may use pg_tunning in you server, following your recomendation.

Other Case, Use pgbounce for those conection.
--
Saludos,
Gilberto Castillo
ETECSA, La Habana, Cuba

Gupta, Amar Nath

unread,
Jul 25, 2016, 3:53:57 AM7/25/16
to
Thanks Scott,

Which of your two dbs has 2,000 connections and needs tuning, the reporting db or the web db?
Amar>> Web DB has 2000 connection. But would be great if you can also suggest tuning for reporting DB.

1: Rarely if ever is 32GB needed for shared_buffers. There's a cost to have more shared_buffers and it's pretty rare that anything over 1 or 2GB is needed. If you have a performance test showing you need more than a few G then yes, go for it.
Amar>> reduced it to 16GB. Honestly speaking I haven’t noticed any difference in DB performance since I reduced memory from 64G to 32GB to 16GB.

2: You've got to get max_connections down to something reasonable. Look at pgbouncer. It's super easy to setup and will allow you to drop the # connections to 100 or so even for busy dbs with lots of users etc.
Amar>> will look into this.

Regards,
Amar

-----Original Message-----
From: Scott Marlowe [mailto:scott....@gmail.com]
Sent: 22 July 2016 17:13
To: Gupta, Amar Nath <ang...@corbus.com>
Cc: pgsql...@postgresql.org
Subject: Re: [ADMIN] High-end PG database configuration help

Confidentiality Notice

This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure.

If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (937-226-7724) or reply to this e-mail and delete all copies of this message.

--

0 new messages