From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pg@fastcrypt.com, Paul Tuckfield <paul@tuckfield.com>
Cc: Anjan Dave <adave@vantage.com>
Cc: Neil Conway <neilc@samurai.com>
Cc: Dirk Lutzebäck <lutzeb@aeccom.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
Date: Thu, 22 Apr 2004 10:37:10 -0700
Message-ID: <200404221037.10097.josh@agliodbs.com> (raw)
In-Reply-To: <20171.1082610827@sss.pgh.pa.us>
References: <200404220456.i3M4uFv04710@candle.pha.pa.us>
<20171.1082610827@sss.pgh.pa.us>
Tom,
> The tricky
> part is that a slow adaptation rate means we can't have every backend
> figuring this out for itself --- the right value would have to be
> maintained globally, and I'm not sure how to do that without adding a
> lot of overhead.
This may be a moot point, since you've stated that changing the loop timing
won't solve the problem, but what about making the test part of make? I
don't think too many systems are going to change processor architectures once
in production, and those that do can be told to re-compile.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, paul@tuckfield.com, adave@vantage.com, neilc@samurai.com, lutzeb@aeccom.com
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
In-Reply-To: <200404221037.10097.josh@agliodbs.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