Re: High CPU Load - Mailing list pgsql-performance

From Markus Schaber
Subject Re: High CPU Load
Date
Msg-id 450A75DE.6050102@logix-tt.com
Whole thread Raw
In response to High CPU Load  (Jérôme BENOIS <benois@argia-engineering.fr>)
Responses Re: High CPU Load  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Re: High CPU Load  (Jérôme BENOIS <benois@argia-engineering.fr>)
List pgsql-performance
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


pgsql-performance by date:

Previous
From: "Joost Kraaijeveld"
Date:
Subject: Why the difference in plans ??
Next
From: Markus Schaber
Date:
Subject: Re: Vacuums on large busy databases