From: Dirk.Lutzebaeck@t-online.de
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgreSQL.org, Neil Conway <neilc@samurai.com>
Subject: Re: Wierd context-switching issue on Xeon
Date: Mon, 19 Apr 2004 23:18:27 +0200
Message-ID: <40844223.9070200@aeccom.com> (raw)
In-Reply-To: <26941.1082397601@sss.pgh.pa.us>
References: <200311251419.36771.josh@agliodbs.com>
<407EFC95.5070805@aeccom.com>
<11437.1082324861@sss.pgh.pa.us>
<200404191050.12833.josh@agliodbs.com>
<26941.1082397601@sss.pgh.pa.us>
I would agree to Tom, that too much parameters are involved to blame
bigmem. I have access to the following machines where the same
application operates:
a) Dual (4way) XEON MP, bigmem, HT off, ServerWorks chipset (a
Fujitsu-Siemens Primergy)
performs ok now because missing indexes were added but this is no proof
that this behaviour occurs again under high load, context switches are
moderate but have peaks to 40.000
b) Dual XEON DP, non-bigmem, HT on, ServerWorks chipset (a Dell machine
I think)
performs moderate because I see too much context switches here although
the mentioned indexes are created, context switches go up to 30.000
often, I can see 50% semop calls
c) Dual XEON DP, non-bigmem, HT on, E7500 Intel chipset (Supermicro)
performs well and I could not observe context switch peaks here (one
user active), almost no extra semop calls
d) Dual XEON DP, bigmem, HT off, ServerWorks chipset (a Fujitsu-Siemens
Primergy)
performance unknown at the moment (is offline) but looks like a) in the past
I can offer to do tests on those machines if somebody would provide me
some test instructions to nail this problem down.
Dirk
Tom Lane wrote:
>Josh Berkus <josh@agliodbs.com> writes:
>
>
>>The other thing I'd like your comment on, Tom, is that Dirk appears to have
>>reported that when he installed a non-bigmem kernel, the issue went away.
>>Dirk, is this correct?
>>
>>
>
>I'd be really surprised if that had anything to do with it. AFAIR
>Dirk's test changed more than one variable and so didn't prove a
>connection.
>
> 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: Dirk.Lutzebaeck@t-online.de, tgl@sss.pgh.pa.us, josh@agliodbs.com, neilc@samurai.com
Subject: Re: Wierd context-switching issue on Xeon
In-Reply-To: <40844223.9070200@aeccom.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