X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D4664D1BABD for ; Wed, 21 Apr 2004 14:30:19 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 51908-03 for ; Wed, 21 Apr 2004 14:30:13 -0300 (ADT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 09197D1BA6C for ; Wed, 21 Apr 2004 14:30:11 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4915415; Wed, 21 Apr 2004 10:31:33 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: pg@fastcrypt.com, =?iso-8859-1?q?Dirk=5FLutzeb=E4ck?= Subject: Re: Wierd context-switching issue on Xeon Date: Wed, 21 Apr 2004 10:29:43 -0700 User-Agent: KMail/1.4.3 Cc: ohp@pyrenet.fr, Tom Lane , Joe Conway , "scott.marlowe" , Bruce Momjian , pgsql-performance@postgresql.org, Neil Conway References: <408664CF.9040507@aeccom.com> <1082559931.1557.235.camel@localhost.localdomain> In-Reply-To: <1082559931.1557.235.camel@localhost.localdomain> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200404211029.43675.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=2.0 tagged_above=0.0 required=5.0 tests=DRASTIC_REDUCED X-Spam-Level: * X-Archive-Number: 200404/355 X-Sequence-Number: 6655 Dave, > After some testing if you use the current head code for s_lock.c which > has some mods in it to alleviate this situation, and change > SPINS_PER_DELAY to 10 you can drastically reduce the cs with tom's test. > I am seeing a slight degradation in throughput using pgbench -c 10 -t > 1000 but it might be liveable, considering the alternative is unbearable > in some situations. > > Can anyone else replicate my results? Can you produce a patch against 7.4.1? I'd like to test your fix against a real-world database. -- Josh Berkus Aglio Database Solutions San Francisco