Re: Spinlocks, yet again: analysis and proposed patches - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Spinlocks, yet again: analysis and proposed patches
Date
Msg-id 200509160940.26337.josh@agliodbs.com
Whole thread Raw
In response to Re: Spinlocks, yet again: analysis and proposed patches  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Spinlocks, yet again: analysis and proposed patches
List pgsql-hackers
Tom,

> What I think this means is that the kernel is scheduling the 2 processes
> onto 2 processors chosen-at-random, without awareness of whether those
> two processors are on the same chip (in the Xeon case) or have closer
> NUMA affinity (in the Opteron case).

That would be consistent with my experience with HT, and the reason why many 
software vendors recommend disabling it.  Not sure about NUMA.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Why does VACUUM FULL bother locking pages?
Next
From: Bruce Momjian
Date:
Subject: Re: Remove xmin and cmin from frozen tuples