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 6B80B32BE02 for ; Fri, 15 Oct 2004 20:53:36 +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 47213-07 for ; Fri, 15 Oct 2004 19:53:28 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C0DE932BDF7 for ; Fri, 15 Oct 2004 20:53:29 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9FJrSJ0020132; Fri, 15 Oct 2004 15:53:28 -0400 (EDT) To: Doug Y Cc: pgsql-performance@postgresql.org Subject: Re: Tuning shared_buffers with ipcs ? In-reply-to: <41701C35.4060808@ptd.net> References: <416FF5BF.8060200@ptd.net> <10905.1097862665@sss.pgh.pa.us> <41701C35.4060808@ptd.net> Comments: In-reply-to Doug Y message dated "Fri, 15 Oct 2004 14:51:33 -0400" Date: Fri, 15 Oct 2004 15:53:28 -0400 Message-ID: <20131.1097870008@sss.pgh.pa.us> From: Tom Lane 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/233 X-Sequence-Number: 8709 Doug Y writes: > Tom Lane wrote: >> I have not seen any such claim, and I do not see any way offhand that >> ipcs could help. >> > Directly from: > http://www.varlena.com/varlena/GeneralBits/Tidbits/annotated_conf_e.html > "As a rule of thumb, observe shared memory usage of PostgreSQL with > tools like ipcs and determine the setting." [ shrug ... ] So ask elein why she thinks that will help. >> This might tell you something about how many concurrent backends you've >> used, but nothing about how many shared buffers you need. >> > Thats strange, I know I've had more than 4 concurrent connections on > that box... (I just checked and there were at least a dozen). There is more than one per-backend semaphore per semaphore set, 16 per set if memory serves; so the ipcs evidence points to a maximum of between 49 and 64 concurrently active backends. It's not telling you a darn thing about appropriate shared_buffers settings, however. > A mirror DB with the same config also has the same basic output from > ipcs, except that it has times for 11 of the 17 arrays slots and most > of them are the time when we do our backup dump (which makes sense > that it would require more memory at that time.) That doesn't follow either. I think you may have some bottleneck that causes client requests to pile up during a backup dump. regards, tom lane