X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 99C54329F2F for ; Tue, 5 Oct 2004 23:37:16 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 77413-05 for ; Tue, 5 Oct 2004 22:37:08 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id E658E329EF2 for ; Tue, 5 Oct 2004 23:37:09 +0100 (BST) Received: from [64.81.245.111] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6462887 for pgsql-performance@postgresql.org; Tue, 05 Oct 2004 15:38:32 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-performance@postgresql.org Subject: Re: Excessive context switching on SMP Xeons Date: Tue, 5 Oct 2004 15:38:51 -0700 User-Agent: KMail/1.6.2 References: <4162CA14.6080206@lulu.com> <200410050947.36174.josh@agliodbs.com> <41630D50.3020308@lulu.com> In-Reply-To: <41630D50.3020308@lulu.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410051538.51664.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/47 X-Sequence-Number: 8523 Bill, > I'd be thrilled to test it too, if for no other reason that to determine > whether what I'm experiencing really is the "CS problem". Hmmm ... Gavin's patch is built against 8.0, and any version of the patch would require linux 2.6, probably 2.6.7 minimum. Can you test on that linux version? Do you have the resources to back-port Gavin's patch? > Fair enough. I never see nearly this much context switching on my dual > Xeon boxes running dozens (sometimes hundreds) of concurrent apache > processes, but I'll concede this could just be due to the more parallel > nature of a bunch of independent apache workers. Certainly could be. Heavy CSes only happen when you have a number of long-running processes with contention for RAM in my experience. If Apache is dispatching thing quickly enough, they'd never arise. > Hence my desire for recommendations on alternate architectures ;-) Well, you could certainly stay on Xeon if there's better support availability. Just get off Dell *650's. > Being a 24x7x365 shop, and these servers being mission critical, I > require vendors that can offer 24x7 4-hour part replacement, like Dell > or IBM. I haven't seen 4-way 64-bit boxes meeting that requirement for > less than $20,000, and that's for a very minimally configured box. A > suitably configured pair will likely end up costing $50,000 or more. I > would like to avoid an unexpected expense of that size, unless there's > no other good alternative. That said, I'm all ears for a cheaper > alternative that meets my support and performance requirements. No, you're going to pay through the nose for that support level. It's how things work. > tps = 369.717832 (including connections establishing) > tps = 370.852058 (excluding connections establishing) Doesn't seem too bad to me. Have anything to compare it to? What's in your postgresql.conf? --Josh