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 BC81A32A232 for ; Fri, 15 Oct 2004 22:18: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 71353-06 for ; Fri, 15 Oct 2004 21:18:13 +0000 (GMT) Received: from neomail03.traderonline.com (email.traderonline.com [65.213.231.10]) by svr1.postgresql.org (Postfix) with ESMTP id E16D632A205 for ; Fri, 15 Oct 2004 22:18:13 +0100 (BST) Received: from [192.168.1.68] (64-139-89-109-ubr02b-epensb01-pa.hfc.comcastbusiness.net [64.139.89.109]) by neomail03.traderonline.com (8.12.10/8.12.8) with ESMTP id i9FKffPG025327; Fri, 15 Oct 2004 16:41:41 -0400 Message-ID: <41703E94.3030800@ptd.net> Date: Fri, 15 Oct 2004 17:18:12 -0400 From: Doug Y User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: Tuning shared_buffers with ipcs ? References: <416FF5BF.8060200@ptd.net> <10905.1097862665@sss.pgh.pa.us> <41701C35.4060808@ptd.net> <20131.1097870008@sss.pgh.pa.us> In-Reply-To: <20131.1097870008@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/240 X-Sequence-Number: 8716 Tom Lane wrote: >Doug Y writes: > > >>Tom Lane wrote: >> >> >>>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 > > Ok, that explains the number of arrays... max_connections / 16. Thanks... my mind works better when I can associate actual settings to effects like that. And I'm sure that performance takes a hit during out back-up dump. We're in the process of migrating them to dedicated mirror machine to run dumps/reports etc from crons so that it won't negatively affect the DB servers that get queries from the web applications. Thanks again for clarification.