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 D75BDD1D52E for ; Mon, 19 Apr 2004 14:55:59 -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 29582-05 for ; Mon, 19 Apr 2004 14:55:51 -0300 (ADT) Received: from mx1.neopolitan.us (mx1.neopolitan.us [65.87.16.224]) by svr1.postgresql.org (Postfix) with ESMTP id 3E6DDD1C9E1 for ; Mon, 19 Apr 2004 14:55:50 -0300 (ADT) Received: from [65.87.16.98] (HELO [10.0.0.210]) by mx1.neopolitan.us (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 3984841 for pgsql-performance@postgresql.org; Mon, 19 Apr 2004 10:55:50 -0700 Subject: Re: Wierd context-switching issue on Xeon From: "J. Andrew Rogers" To: pgsql-performance@postgresql.org In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509813F@vt-pe2550-001.vantage.vantage.com> References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509813F@vt-pe2550-001.vantage.vantage.com> Content-Type: text/plain Organization: Message-Id: <1082397350.30934.34.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 19 Apr 2004 10:55:50 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/274 X-Sequence-Number: 6574 I decided to check the context-switching behavior here for baseline since we have a rather diverse set of postgres server hardware, though nothing using Xeon MP that is also running a postgres instance, and everything looks normal under load. Some platforms are better than others, but nothing is outside of what I would consider normal bounds. Our biggest database servers are Opteron SMP systems, and these servers are particularly well-behaved under load with Postgres 7.4.2. If there is a problem with the locking code and context-switching, it sure isn't manifesting on our Opteron SMP systems. Under rare confluences of process interaction, we occasionally see short spikes in the 2-3,000 cs/sec range. It typically peaks at a couple hundred cs/sec under load. Obviously this is going to be a function of our load profile a certain extent. The Opterons have proven to be very good database hardware in general for us. j. andrew rogers