X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id A4352B430A6 for ; Sun, 6 Jul 2003 10:27:17 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 96074-10 for ; Sun, 6 Jul 2003 07:26:45 -0300 (ADT) Received: from ethereal-realms.org (thebe.ethereal-realms.org [142.179.222.205]) by svr1.postgresql.org (Postfix) with ESMTP id 66B2EB430A9 for ; Sun, 6 Jul 2003 07:26:44 -0300 (ADT) Received: from ethereal-realms.org (ip14.ethereal-realms.COM [192.168.1.14]) by ethereal-realms.org (8.12.6/8.12.6) with ESMTP id h66AQNPu008093; Sun, 6 Jul 2003 04:26:23 -0600 (MDT) Message-ID: <3F07F94D.50406@ethereal-realms.org> Date: Sun, 06 Jul 2003 04:26:21 -0600 From: Martin Foster Organization: Ethereal Realms User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Postgresql Performance Cc: "Shridhar Daithankar" Subject: Re: Extreme high load averages References: <3F083CCA.31144.7468C@localhost> In-Reply-To: <3F083CCA.31144.7468C@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/110 X-Sequence-Number: 2403 Shridhar Daithankar wrote: > On 5 Jul 2003 at 22:54, Martin Foster wrote: > >>What I would like to know is. Why? The kernel has been compiled to >>handle the number of concurrent connections, the server may not be the >>best, but it should be able to handle the requests: PIII 1Ghz, 1GB >>SDRAM, 2 IDE 20GB drives. >> >>I have changed settings to take advantage of the memory. So the >>following settings are of interest: >> shared_buffers = 16384 >> wal_buffers = 256 >> sort_mem = 16384 >> vacuum_mem = 32768 > > > As somebody else has already pointed out, your sort_mem is bit too high > than required. Try lowering it. > > Secondly did you tune effective_cache_size? > > HTH > Bye > Shridhar > > -- > Power, n.: The only narcotic regulated by the SEC instead of the FDA. > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly I dropped the size of the sort_mem down to 8 megs. Since I am not swapping to cache at all this should not post much of a problem at that value. effective_cache_size seems interesting, though the description is somewhat lacking. Is this related to the swap partition and how much of it will be used by PostgreSQL? If I am correct, this should be fairly low? Martin Foster Creator/Designer Ethereal Realms martin@ethereal-realms.org