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 DECD8D1B97B for ; Tue, 4 May 2004 04:37:48 -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 25372-10 for ; Tue, 4 May 2004 04:37:29 -0300 (ADT) Received: from linda-2.paradise.net.nz (bm-2a.paradise.net.nz [202.0.58.21]) by svr1.postgresql.org (Postfix) with ESMTP id 73FCDD1B8A2 for ; Tue, 4 May 2004 04:37:27 -0300 (ADT) Received: from smtp-2.paradise.net.nz (smtp-2b.paradise.net.nz [202.0.32.211]) by linda-2.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HX600KMGIIF30@linda-2.paradise.net.nz> for pgsql-performance@postgresql.org; Tue, 04 May 2004 19:37:27 +1200 (NZST) Received: from paradise.net.nz (218-101-12-151.paradise.net.nz [218.101.12.151]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id E3DE79E2AE; Tue, 04 May 2004 19:37:26 +1200 (NZST) Date: Tue, 04 May 2004 19:39:22 +1200 From: Mark Kirkwood Subject: Re: Fwd: FreeBSD, PostgreSQL, semwait and sbwait! In-reply-to: <52623D23-9AA4-11D8-9268-000A95DE2550@gdr-isis.enst.fr> To: =?ISO-8859-1?Q?Pailloncy_Jean-G=E9rard?= Cc: pgsql-performance@postgresql.org Message-id: <409748AA.2030801@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040404 References: <200403231248.34425.darcy@wavefire.com> <40615443.4030003@paradise.net.nz> <52623D23-9AA4-11D8-9268-000A95DE2550@gdr-isis.enst.fr> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=2.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_BL_SPAMCOP_NET X-Spam-Level: ** X-Archive-Number: 200405/21 X-Sequence-Number: 6852 I am wondering if your wait is caused by contention between pg_autovacuum and the DELETE that is running. Your large Pg blocksize (32K) *may* be contributing to any possible contention as well. Maybe try disabling pg_autovacuum to see if there is any change in behaviour. Also going through my head is '32 Kb bock's size (to match ffs and raid block's size)' - does that mean you have raid strip size = 32K? maybe try 128K (I know it sounds like a bad thing, but generally raid stripes of 128K->256K are better than 32K->64K) regards Mark Pailloncy Jean-Gérard wrote: > Hello, > >> > I found the same problem. > > I use OpenBSD 3.3, > On Pentium 2,4 GHz with 1 Gb RAM, RAID 10. > With PostgreSQL 7.4.1 with 32 Kb bock's size (to match ffs and raid > block's size) > With pg_autovacuum daemon from Pg 7.5. > > I run a web indexer. > sd0 raid-1 with system pg-log and indexer-log > sd1 raid-10 with pg-data and indexer-data > The sd1 disk achives between 10 and 40 Mb/s on normal operation. > > When I get semwait in top, system waits ;-) > Not much disk activity. > Not much log in pg or indexer. > Just wait.... >