pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
RAM usage per connection
3+ messages / 2 participants
[nested] [flat]

* RAM usage per connection
@ 2004-05-12 18:39  Steve Lane <slane@moyergroup.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Steve Lane @ 2004-05-12 18:39 UTC (permalink / raw)
  To: pgsql-admin

Hello all:

I have a customer with an application in production (postgres + php +
apache) where we began seeing a  number of scary messages in the logs. (It's
postgres 7.2.1, by the way).

Generally the messages seem to point to resource starvation of some kind:

FATAL 1:  out of free buffers: time to abort !


And 

Sorry, too many clients already

Also some messages indicating shared memory had been corrupted. I shut down
and ran ipcclean and those messages are gone. I also boosted shared-buffers
considerably and the "out of free buffers" message is also gone.

BUT, the "sorry too many clients" message persists. The app has a spike-y
usage pattern, i.e. A large number of students sits down at once and takes a
survey in accordance with verabl instructions from the front of the
classroom, so many of them are hitting the proverbial Submit button at once.

I tried increasing max_clients, but got a message to the effect that SHMMIN
was set incorrectly on my machine ...

Let me get to my actual question (none of the above contains the question
yet :->).

Is there any guideline as to how much free RAM I need per client connection?
I think I understand that things like sort_mem play into this -- that's set
low and should remain so. But for Apache, for example, I think of 10 meg per
connection. Any similar rule of thumb for postgres?

I'll follow up as I inspect the logs, but I haven't thoroughly sifted them.
So for my now my question is the one about RAM per connection.  Any
thoughts'd be much appreciated.

-- sgl


=======================================================
Steve Lane

Vice President
The Moyer Group
14 North Peoria St Suite 2H
Chicago, IL 60607

Voice: (312) 433-2421       Email: slane@moyergroup.com
Fax:   (312) 850-3930       Web:   http://www.moyergroup.com
=======================================================




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: RAM usage per connection
@ 2004-05-12 20:13  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Steve Lane <slane@moyergroup.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2004-05-12 20:13 UTC (permalink / raw)
  To: Steve Lane <slane@moyergroup.com>; +Cc: pgsql-admin

Steve Lane <slane@moyergroup.com> writes:
> I have a customer with an application in production (postgres + php +
> apache) where we began seeing a  number of scary messages in the logs. (It's
> postgres 7.2.1, by the way).
  ^^^^^^^^^^^^^^

Reading the CVS logs for post-7.2.1 bug fixes will curl your toes.
You're irresponsible to still be running production data on that
version.  Move up to 7.2.4 before you find out the hard way.

> I tried increasing max_clients, but got a message to the effect that SHMMIN
> was set incorrectly on my machine ...

I'd expect SHMMAX to be the issue not SHMMIN.  It's set very
conservatively on many platforms, and you should not be afraid to raise
it.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: RAM usage per connection
@ 2004-05-13 00:15  Steve Lane <slane@moyergroup.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Steve Lane @ 2004-05-13 00:15 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin



> From: Tom Lane <tgl@sss.pgh.pa.us>
> Date: Wed, 12 May 2004 16:13:37 -0400
> To: Steve Lane <slane@moyergroup.com>
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] RAM usage per connection
> 
> Steve Lane <slane@moyergroup.com> writes:
>> I have a customer with an application in production (postgres + php +
>> apache) where we began seeing a  number of scary messages in the logs. (It's
>> postgres 7.2.1, by the way).
> ^^^^^^^^^^^^^^
> 
> Reading the CVS logs for post-7.2.1 bug fixes will curl your toes.
> You're irresponsible to still be running production data on that
> version.  Move up to 7.2.4 before you find out the hard way.

I spoke too hastily. It's 7.1.3. Which probably doesn't make it better :-(
> 
>> I tried increasing max_clients, but got a message to the effect that SHMMIN
>> was set incorrectly on my machine ...
> 
> I'd expect SHMMAX to be the issue not SHMMIN.  It's set very
> conservatively on many platforms, and you should not be afraid to raise
> it.

I was also puzzled to see the reference to SHMMIN. I'll look again.

-- steve




^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2004-05-13 00:15 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-05-12 18:39 RAM usage per connection Steve Lane <slane@moyergroup.com>
2004-05-12 20:13 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-05-13 00:15   ` Steve Lane <slane@moyergroup.com>

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