From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dirk Lutzebäck <lutzeb@aeccom.com>
Cc: josh@agliodbs.com, pgsql-performance@postgresql.org, Sven Geisler <sgeisler@aeccom.com>
Subject: Re: RESOLVED: Re: Wierd context-switching issue on Xeon
Date: Fri, 16 Apr 2004 09:49:38 -0400
Message-ID: <28603.1082123378@sss.pgh.pa.us> (raw)
In-Reply-To: <407FD9A0.6040608@aeccom.com>
References: <200311251419.36771.josh@agliodbs.com>
<200404150827.03950.josh@agliodbs.com>
<407EB5B0.3030706@aeccom.com>
<200404151039.17763.josh@agliodbs.com>
<407EE93F.3090705@aeccom.com>
<21280.1082064326@sss.pgh.pa.us>
<407F9FE9.3060104@aeccom.com>
<407FAF0F.2070304@aeccom.com>
<407FD9A0.6040608@aeccom.com>
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb@aeccom.com> writes:
> This was the key to look at: we were missing all indices on table which
> is used heavily and does lots of locking. After recreating the missing
> indices the production system performed normal. No, more excessive
> semop() calls, load way below 1.0, CS over 20.000 very rare, more in
> thousands realm and less.
Hmm ... that's darn interesting. AFAICT the test case I am looking at
for Josh's client has no such SQL-level problem ... but I will go back
and double check ...
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, lutzeb@aeccom.com, sgeisler@aeccom.com
Subject: Re: RESOLVED: Re: Wierd context-switching issue on Xeon
In-Reply-To: <28603.1082123378@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