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 D224CD1E104 for ; Tue, 23 Mar 2004 23:00:43 +0000 (GMT) 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 70768-03 for ; Tue, 23 Mar 2004 19:00:44 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 1CAF1D1DCC0 for ; Tue, 23 Mar 2004 19:00:41 -0400 (AST) 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 i2NN0fSl007577; Tue, 23 Mar 2004 18:00:41 -0500 (EST) To: josh@agliodbs.com Cc: Darcy Buskermolen , pgsql-performance@postgresql.org Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait! In-reply-to: <200403231455.08334.josh@agliodbs.com> References: <200403231248.34425.darcy@wavefire.com> <7083.1080080273@sss.pgh.pa.us> <200403231455.08334.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 23 Mar 2004 14:55:08 -0800" Date: Tue, 23 Mar 2004 18:00:40 -0500 Message-ID: <7576.1080082840@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/338 X-Sequence-Number: 6194 Josh Berkus writes: > Forget hyperthreading. Look at their postgresql.conf settings. 8mb shared > mem, 16mb sort mem per connection for 512 connections, default > effective_cache_size. They could well be going into swap hell due to the oversized sort_mem, but that didn't quite seem to explain the reported behavior. I'd want to see vmstat or similar output to confirm whether the disks are busy, though. Amazing how many people forget that a database is normally I/O-bound rather than CPU-bound. regards, tom lane