From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-performance@postgresql.org
Subject: Re: High CPU Load
Date: Fri, 15 Sep 2006 11:43:58 +0200
Message-ID: <450A75DE.6050102@logix-tt.com> (raw)
In-Reply-To: <1158239339.5226.17.camel@localhost.localdomain>
References: <1158239339.5226.17.camel@localhost.localdomain>
Hi, Jérôme,
Jérôme BENOIS wrote:
> max_connections = 512
Do you really have that much concurrent connections? Then you should
think about getting a larger machine, probably.
You will definitely want to play with commit_delay and commit_siblings
settings in that case, especially if you have write access.
> work_mem = 65536
> effective_cache_size = 131072
hmm, 131072*8*1024 + 512*65536*1024 = 35433480192 - thats 33 Gig of
Memory you assume here, not counting OS usage, and the fact that certain
queries can use up a multiple of work_mem.
Even on amachine that big, I'd be inclined to dedicate more memory to
caching, and less to the backends, unless specific needs dictate it. You
could try to use sqlrelay or pgpool to cut down the number of backends
you need.
> My Server is Dual Xeon 3.06GHz
For xeons, there were rumours about "context switch storms" which kill
performance.
> with 2 Go RAM and good SCSI disks.
For 2 Gigs of ram, you should cut down the number of concurrent backends.
Does your machine go into swap?
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
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: schabi@logix-tt.com
Subject: Re: High CPU Load
In-Reply-To: <450A75DE.6050102@logix-tt.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