From: Tom Lane <tgl@sss.pgh.pa.us>
To: Darcy Buskermolen <darcy@wavefire.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait!
Date: Tue, 23 Mar 2004 17:17:53 -0500
Message-ID: <7083.1080080273@sss.pgh.pa.us> (raw)
In-Reply-To: <200403231248.34425.darcy@wavefire.com>
References: <200403231248.34425.darcy@wavefire.com>
Darcy Buskermolen <darcy@wavefire.com> writes:
> The database server is a dual P4-2.8 w/ HT enabled (kernel finds 4
> processors), 2GB RAM, 4 disk Serial ATA on 3ware RAID, gigabit Ethernet
> connection to web servers. It's running FreeBSD 5.2 and PostgreSQL 7.4.1.
Hm. What happens if you turn off the hyperthreading?
We have seen a number of reports recently that suggest that our
spinlocking code behaves inefficiently on hyperthreaded machines.
This hasn't got to the point where we have any substantiated evidence,
mind you, but maybe you can help provide some.
Also it might be interesting to put one of these into the outer loop in
s_lock():
__asm__ __volatile__(
" rep; nop \n"
: : : "memory");
(This suggestion is a quick-and-dirty backport of a change that's
already in CVS tip.)
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, darcy@wavefire.com
Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait!
In-Reply-To: <7083.1080080273@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