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 CB4935E3AC5 for ; Fri, 6 Aug 2004 19:58:41 -0300 (ADT) 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 45471-06 for ; Fri, 6 Aug 2004 22:58:36 +0000 (GMT) Received: from fep3.cogeco.net (smtp.cogeco.net [216.221.81.25]) by svr1.postgresql.org (Postfix) with ESMTP id AD7815E46C5 for ; Fri, 6 Aug 2004 19:58:31 -0300 (ADT) Received: from [127.0.0.1] (d226-86-215.home.cgocable.net [24.226.86.215]) by fep3.cogeco.net (Postfix) with ESMTP id 08C902F0A; Fri, 6 Aug 2004 18:58:35 -0400 (EDT) Message-ID: <41140D17.7070101@ethereal-realms.org> Date: Fri, 06 Aug 2004 18:58:31 -0400 From: Martin Foster User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-ca, en-gb, en-us, en MIME-Version: 1.0 To: Gaetano Mendola , PostgreSQL Performance Subject: Re: Performance Bottleneck References: <410FDC53.5080509@bigfoot.com> <4110FFF6.1030001@bigfoot.com> In-Reply-To: <4110FFF6.1030001@bigfoot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200408/82 X-Sequence-Number: 7718 Gaetano Mendola wrote: > > > Let start from your postgres configuration: > > shared_buffers = 8192 <==== This is really too small for your > configuration > sort_mem = 2048 > > wal_buffers = 128 <==== This is really too small for your configuration > > effective_cache_size = 16000 > > change this values in: > > shared_buffers = 50000 > sort_mem = 16084 > > wal_buffers = 1500 > > effective_cache_size = 32000 > > > to bump up the shm usage you have to configure your OS in order to be > allowed to use that ammount of SHM. > > This are the numbers that I feel good for your HW, the second step now is > analyze your queries > These changes have yielded some visible improvements, with load averages rarely going over the anything noticeable. However, I do have a question on the matter, why do these values seem to be far higher then what a frequently pointed to document would indicate as necessary? http://www.varlena.com/GeneralBits/Tidbits/perf.html I am simply curious, as this clearly shows that my understanding of PostgreSQL is clearly lacking when it comes to tweaking for the hardware. Martin Foster Creator/Designer Ethereal Realms martin@ethereal-realms.org