pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Ryan King - NOAA Affiliate <ryan.king@noaa.gov>
Cc: Scott Whitney <scott@journyx.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: could not create shared memory segment: Invalid argument
Date: Mon, 13 Jul 2015 19:15:12 -0600
Message-ID: <35EBDB73-CF15-40D6-8AEB-F31AF39FDD5D@elevated-dev.com> (raw)
In-Reply-To: <CAJAJqWHiO=0Ah429WPXX4c2W8at8W=1oy5ZRzPubFW=RA9BunQ@mail.gmail.com>
References: <68lu4k8tv291mdsfmpf9wvf5.1436832911969@email.android.com>
	<CAJAJqWFwm5wrqD4hWtmooXiR9eK9xuqs9pvfOZG8ZKBCPMTXbQ@mail.gmail.com>
	<9CBF373D-FFB2-4094-8316-176B1D4F936D@elevated-dev.com>
	<CAJAJqWHiO=0Ah429WPXX4c2W8at8W=1oy5ZRzPubFW=RA9BunQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On Jul 13, 2015, at 6:49 PM, Ryan King - NOAA Affiliate <ryan.king@noaa.gov> wrote:
> 
> Yeah thanks I see I was going the wrong way...thanks. 
> So shared_buffers is 15gb and max_conn = 1000. 

OK, you haven't shared your OS or hardware setup, but a few general points:

- 15GB is large for PG shared buffers; it usually doesn't help to go that high; remember, shared buffers is a kind of working cache, not the whole cache, PG depends on the OS caching of recently-used files;

- Your shmall is only 16GB. PG may not be the only user of shared memory. It doesn't make sense to have shmall * page size < shmmax.

- Also, does your platform have some absolute upper limit on shmmax? 250GB seems awfully high...

- With 1,000 clients, you'd likely benefit from connection pooling; after you get things up, you should consider pgbouncer.

-- 
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice







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



view thread (10+ messages)  latest in thread

Message-ID: <35EBDB73-CF15-40D6-8AEB-F31AF39FDD5D@elevated-dev.com>
Permalink:  ../35EBDB73-CF15-40D6-8AEB-F31AF39FDD5D@elevated-dev.com/
Also on:    postgresql.org/message-id/35EBDB73-CF15-40D6-8AEB-F31AF39FDD5D@elevated-dev.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: scott_ribe@elevated-dev.com, ryan.king@noaa.gov, scott@journyx.com, pgsql-admin@postgresql.org
  Subject: Re: could not create shared memory segment: Invalid argument
  In-Reply-To: <35EBDB73-CF15-40D6-8AEB-F31AF39FDD5D@elevated-dev.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox