From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Simon Sadedin <pg_sicko@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: poor cpu utilization on dual cpu box
Date: Wed, 22 Oct 2003 13:02:56 -0400
Message-ID: <17145.1066842176@sss.pgh.pa.us> (raw)
In-Reply-To: <200310220911.14853.josh@agliodbs.com>
References: <20031022145757.80993.qmail@web12603.mail.yahoo.com>
<200310220911.14853.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
>> We are running with shared buffers large enough to hold the
>> entire database
> Which is bad. This is not what shared buffers are for. See:
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
In fact, that may be the cause of the performance issue. The high
context-swap rate suggests heavy contention for shared-memory data
structures. The first explanation that occurs to me is that too much
time is being spent managing the buffer hashtable, causing that to
become a serialization bottleneck. Try setting shared_buffers to 10000
or so and see if it gets better.
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com, pg_sicko@yahoo.com
Subject: Re: poor cpu utilization on dual cpu box
In-Reply-To: <17145.1066842176@sss.pgh.pa.us>
* 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