pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: MindTerm <mindterm@yahoo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: performance tuning in large function / transaction
Date: Thu, 13 Dec 2001 22:40:57 -0800 (PST)
Message-ID: <20011213223847.X8121-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <GNELIHDDFBOCMGBFGEFOAEMGCAAA.chriskl@familyhealth.com.au>

On Fri, 14 Dec 2001, Christopher Kings-Lynne wrote:

> Hmmm...
>
> I have a database server for a website for which I am 'dedicating' at least
> 128MB of ram (I could say that it can have 256MB)
>
> I have max_connections 64
> and shared_buffers 256
> and sort_mem 1024
>
> Is that really small?
>
> I have this SHM config:
>
> options         SYSVSHM
> options         SYSVMSG
> options         SYSVSEM
>
> options         SHMMAXPGS=16384         # 64MB shared mem?
> #options        SHMALL=1025             # max kb of shared mem
> options         SHMSEG=256              # 256 shared segs per proc
>
> options         SEMMNI=256              # 256 semaphore identifiers
> options         SEMMNS=512              # 512 semaphores in the system
> options         SEMMNU=256              # 256 undo structures in system
> options         SEMMAP=256              # 256 entries in semaphore map
>
> How do you calculate the shared memory required by postgres given the
> shared_buffers value???

IIRC each buffer is 8k, so 256 shared buffers is still pretty small.

sort_mem is wierd due to the way it's used (I think that's per sort, so
maybe you could get more than that per backend if a query had multiple
sort steps), but I think that's backend local memory not shared.




view thread (23+ messages)  latest in thread

Message-ID: <20011213223847.X8121-100000@megazone23.bigpanda.com>
Permalink:  ../20011213223847.X8121-100000@megazone23.bigpanda.com/
Also on:    postgresql.org/message-id/20011213223847.X8121-100000@megazone23.bigpanda.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-sql@postgresql.org
  Cc: sszabo@megazone23.bigpanda.com, chriskl@familyhealth.com.au, mindterm@yahoo.com
  Subject: Re: performance tuning in large function / transaction
  In-Reply-To: <20011213223847.X8121-100000@megazone23.bigpanda.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