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 76BA3D1DD51 for ; Mon, 19 Apr 2004 21:53:57 -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 80625-04 for ; Mon, 19 Apr 2004 21:53:59 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 74A3AD1DC7D for ; Mon, 19 Apr 2004 21:53:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3K0r9aj001932; Mon, 19 Apr 2004 20:53:09 -0400 (EDT) To: josh@agliodbs.com Cc: Joe Conway , "scott.marlowe" , Bruce Momjian , lutzeb@aeccom.com, pgsql-performance@postgresql.org, Neil Conway Subject: Re: Wierd context-switching issue on Xeon In-reply-to: <1407.1082419316@sss.pgh.pa.us> References: <40843E63.7050101@joeconway.com> <200404191455.04068.josh@agliodbs.com> <1407.1082419316@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 19 Apr 2004 20:01:56 -0400" Date: Mon, 19 Apr 2004 20:53:09 -0400 Message-ID: <1931.1082422389@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/282 X-Sequence-Number: 6582 I wrote: > Here is a test case. Hmmm ... I've been able to reproduce the CS storm on a dual Athlon, which seems to pretty much let the Xeon per se off the hook. Anybody got a multiple Opteron to try? Totally non-Intel CPUs? It would be interesting to see results with non-Linux kernels, too. regards, tom lane