X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 89CB9D1DFFC for ; Wed, 12 May 2004 08:08:47 -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 21103-02 for ; Wed, 12 May 2004 08:08:29 -0300 (ADT) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) by svr1.postgresql.org (Postfix) with ESMTP id B0D29D1D754 for ; Wed, 12 May 2004 08:08:23 -0300 (ADT) Received: from dcave.digsys.bg (daniel@localhost.digsys.bg [127.0.0.1]) by dcave.digsys.bg (8.11.6/8.10.1) with ESMTP id i4CB84v05681; Wed, 12 May 2004 14:08:04 +0300 (EEST) Message-Id: <200405121108.i4CB84v05681@dcave.digsys.bg> X-Mailer: exmh version 2.1.0 09/18/1999 To: Halford Dace Cc: pgsql-admin@postgresql.org Subject: Re: [PERFORM] Quad processor options In-reply-to: Your message of "Wed, 12 May 2004 12:27:18 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 2004 14:08:04 +0300 From: Daniel Kalchev X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/106 X-Sequence-Number: 13422 It appears that your CPU is 'slow' while your disk subsystem is 'fast'. I had once such situation with 15 kRPM drives and ~500MHz Pentium III. On that system, the best solution was to either increase effective_cache_size or decrease random_page_cost (the latter obviously has to do with the fast disk, the former with the lots of RAM). In any case, proper optimization of queries always helps. :-) Daniel >>>Halford Dace said: > > On 12 May 2004, at 12:17 PM, Manfred Koizar wrote: > > > On Tue, 11 May 2004 15:46:25 -0700, Paul Tuckfield > > wrote: > > > >> - I'll bet you have a low value for shared buffers, like 10000. On > >> your 3G system > >> you should ramp up the value to at least 1G (125000 8k buffers) > > > > In most cases this is almost the worst thing you can do. The only > > thing > > even worse would be setting it to 1.5 G. > > > > Postgres is just happy with a moderate shared_buffers setting. We > > usually recommend something like 10000. You could try 20000, but don't > > increase it beyond that without strong evidence that it helps in your > > particular case. > > > > This has been discussed several times here, on -hackers and on > > -general. > > Search the archives for more information. > > We have definitely found this to be true here. We have some fairly > complex queries running on a rather underpowered box (beautiful but > steam-driven old Silicon Graphics Challenge DM). We ended up using a > very slight increase to shared buffers, but gaining ENORMOUSLY through > proper optimisation of queries, appropriate indices and the use of > optimizer-bludgeons like "SET ENABLE_SEQSCAN = OFF" > > Hal > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org