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 29D75D1ECB2 for ; Wed, 24 Mar 2004 09:24:59 +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 79178-05 for ; Wed, 24 Mar 2004 05:24:57 -0400 (AST) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [202.0.58.22]) by svr1.postgresql.org (Postfix) with ESMTP id 807C0D1ECAF for ; Wed, 24 Mar 2004 05:24:54 -0400 (AST) Received: from smtp-1.paradise.net.nz (smtp-1b.paradise.net.nz [202.0.32.210]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HV20010PQ5JGS@linda-3.paradise.net.nz> for pgsql-performance@postgresql.org; Wed, 24 Mar 2004 21:24:55 +1200 (NZST) Received: from paradise.net.nz (218-101-13-54.paradise.net.nz [218.101.13.54]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 0B9DE83068; Wed, 24 Mar 2004 21:24:55 +1200 (NZST) Date: Wed, 24 Mar 2004 21:26:27 +1200 From: Mark Kirkwood Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait! In-reply-to: <200403231248.34425.darcy@wavefire.com> To: Darcy Buskermolen Cc: pgsql-performance@postgresql.org Message-id: <40615443.4030003@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031213 References: <200403231248.34425.darcy@wavefire.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/344 X-Sequence-Number: 6200 Darcy Buskermolen wrote: >---------- Forwarded Message ---------- > >Subject: FreeBSD, PostgreSQL, semwait and sbwait! >Date: March 23, 2004 12:02 pm >From: "Jason Coene" >To: > >Hello all, > >We're having a substantial problem with our FreeBSD 5.2 database server >running PostgreSQL - it's getting a lot of traffic (figure about 3,000 >queries per second), but queries are slow, and it's seemingly waiting on >other things than CPU time > > Could this be a 5.2 performance issue ? In spite of certain areas where the 5.x series performance is known to be much better than 4.x (e.g networking), this may not be manifested in practice for a complete application. (e.g. I am still running 4.9 as it outperformed 5.1 vastly for a ~100 database sessions running queries - note that I have not tried out 5.2, so am happy to be corrected on this) regards Mark