From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Darcy Buskermolen <darcy@wavefire.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait!
Date: Tue, 23 Mar 2004 18:00:40 -0500
Message-ID: <7576.1080082840@sss.pgh.pa.us> (raw)
In-Reply-To: <200403231455.08334.josh@agliodbs.com>
References: <200403231248.34425.darcy@wavefire.com>
<7083.1080080273@sss.pgh.pa.us>
<200403231455.08334.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Forget hyperthreading. Look at their postgresql.conf settings. 8mb shared
> mem, 16mb sort mem per connection for 512 connections, default
> effective_cache_size.
They could well be going into swap hell due to the oversized sort_mem,
but that didn't quite seem to explain the reported behavior. I'd want
to see vmstat or similar output to confirm whether the disks are busy,
though. Amazing how many people forget that a database is normally
I/O-bound rather than CPU-bound.
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, darcy@wavefire.com
Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait!
In-Reply-To: <7576.1080082840@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