Skip site navigation (1) Skip section navigation (2)

Re: Wierd context-switching issue on Xeon patch for 7.4.1

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pg(at)fastcrypt(dot)com,Paul Tuckfield <paul(at)tuckfield(dot)com>, Anjan Dave <adave(at)vantage(dot)com>,Neil Conway <neilc(at)samurai(dot)com>,Dirk Lutzeb├Ąck <lutzeb(at)aeccom(dot)com>,Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
Date: 2004-04-22 21:22:11
Message-ID: 1082668930.94537.0.camel@jester (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, 2004-04-22 at 13:55, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > 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.
> 
> Having to recompile to run on single- vs dual-processor machines doesn't
> seem like it would fly.

Is it something the postmaster could quickly determine and set a global
during the startup cycle?



In response to

pgsql-performance by date

Next:From: Sean ShannyDate: 2004-04-22 21:56:59
Subject: Looking for ideas on how to speed up warehouse loading
Previous:From: Magnus HaganderDate: 2004-04-22 21:21:33
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group