From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul Tuckfield <paul@tuckfield.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon
Date: Wed, 21 Apr 2004 23:10:43 -0400
Message-ID: <18620.1082603443@sss.pgh.pa.us> (raw)
In-Reply-To: <9D274446-932B-11D8-BA67-000393BD6C3E@tuckfield.com>
References: <Pine.LNX.4.33.0404191410550.17372-100000@css120.ihs.com>
<40843E63.7050101@joeconway.com>
<200404191455.04068.josh@agliodbs.com>
<1407.1082419316@sss.pgh.pa.us>
<1931.1082422389@sss.pgh.pa.us>
<AF7EFDBC-9305-11D8-BA67-000393BD6C3E@tuckfield.com>
<9D274446-932B-11D8-BA67-000393BD6C3E@tuckfield.com>
Paul Tuckfield <paul@tuckfield.com> writes:
>> I used the taskset command:
>> taskset 01 -p <pid for backend of test_run.sql 1>
>> taskset 01 -p <pid for backend of test_run.sql 1>
>>
>> I guess that 0 and 1 are the two cores (pipelines? hyper-threads?) on
>> the first Xeon processor in the box.
AFAICT, what you've actually done here is to bind both backends to the
first logical processor of the first Xeon. If you'd used 01 and 02
as the affinity masks then you'd have bound them to the two cores of
that Xeon, but what you actually did simply reduces the system to a
uniprocessor. In that situation the context swap rate will be normally
one swap per scheduler timeslice, and at worst two swaps per timeslice
(if a process is swapped away from while it holds a lock the other one
wants). It doesn't prove a lot about our SMP problem though.
I don't have access to a Xeon with both taskset and hyperthreading
enabled, so I can't check what happens when you do the taskset correctly
... could you retry?
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, paul@tuckfield.com
Subject: Re: Wierd context-switching issue on Xeon
In-Reply-To: <18620.1082603443@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