From: Dirk Lutzebäck <lutzeb@aeccom.com>
To: josh@agliodbs.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: RESOLVED: Re: Wierd context-switching issue on Xeon
Date: Mon, 19 Apr 2004 09:27:57 +0200
Message-ID: <40837F7D.9050102@aeccom.com> (raw)
In-Reply-To: <200404160958.14902.josh@agliodbs.com>
References: <200311251419.36771.josh@agliodbs.com>
<407FAF0F.2070304@aeccom.com>
<407FD9A0.6040608@aeccom.com>
<200404160958.14902.josh@agliodbs.com>
Josh, I cannot reproduce the excessive semop() on a Dual XEON DP on a
non-bigmem kernel, HT on. Interesting to know if the problem is related
to XEON MP (as Tom wrote) or bigmem.
Josh Berkus wrote:
>Dirk,
>
>
>
>>I'm not sure if this semop() problem is still an issue but the database
>>behaves a bit out of bounds in this situation, i.e. consuming system
>>resources with semop() calls 95% while tables are locked very often and
>>longer.
>>
>>
>
>It would be helpful to us if you could test this with the indexes disabled on
>the non-Bigmem system. I'd like to eliminate Bigmem as a factor, if
>possible.
>
>
>
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: lutzeb@aeccom.com, josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: RESOLVED: Re: Wierd context-switching issue on Xeon
In-Reply-To: <40837F7D.9050102@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