pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Kavan, Dan (IMS) <KavanD@imsweb.com>
Cc: postgres <pgsql-admin@postgresql.org>
Subject: Re: memory allocation ; postgresql-8.0
Date: Thu, 12 May 2005 10:20:53 -0500
Message-ID: <1115911253.3868.262.camel@state.g2switchworks.com> (raw)
In-Reply-To: <782D2A81EC812642B857B03B506E0B44326488@granite.omni.imsweb.com>
References: <782D2A81EC812642B857B03B506E0B44326488@granite.omni.imsweb.com>

On Thu, 2005-05-12 at 10:10, Kavan, Dan (IMS) wrote:
> Hi Scott,
> 
> Thanks again for all your tips.
> 
> If I knock the buffer size down to 65,536 (still higher than what you
> are recommending)  then my shmmax becomes:
> 256,000 + 550,292,685 (65536*8396.8) + 1,454,100 = 552,002,785  
> 
> That will leave me with 3.5 GB of free memory for the system & work
> memory to use.
> Will those free system resources ever get used with a 10 million record,
> 10 GB database?

Certainly.  As you access the data the kernel will cache all the data
sent through it.  Once the machine's been up and processing for a while
you should see a top output that shows "free" memory at a few megs (8 to
30 meg is typical) and all the rest of the memory being used as kernel
cache.

> If I go with 65,536 as my buffer size, Would having the SHMMAX set to 1
> GB on my sysctl.conf system parameters allow me to run two seperate
> instances of postgresql on 2 seperate ports?

Yes, but you may want to set it just a tad higher for things like fsm
and whatnot.

Definitely benchmark both the 64k setting of shared_buffers and lower
settings, looking for a knee with your data set.  It may well be that
the best performance happens at a lower number, and doesn't really
increase as you bump up the shared_buffers.  Be sure to test things as
realistically as possible, i.e. the right amount of parallel users and
all that.



view thread (6+ messages)  latest in thread

Message-ID: <1115911253.3868.262.camel@state.g2switchworks.com>
Permalink:  ../1115911253.3868.262.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1115911253.3868.262.camel@state.g2switchworks.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, KavanD@imsweb.com
  Subject: Re: memory allocation ; postgresql-8.0
  In-Reply-To: <1115911253.3868.262.camel@state.g2switchworks.com>
  References: <782D2A81EC812642B857B03B506E0B44326488@granite.omni.imsweb.com> <1115911253.3868.262.camel@state.g2switchworks.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