pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Daniel Kalchev <daniel@digsys.bg>
To: Halford Dace <hal@stowe.co.za>
Cc: pgsql-admin@postgresql.org
Subject: Re: [PERFORM] Quad processor options
Date: Wed, 12 May 2004 14:08:04 +0300
Message-ID: <200405121108.i4CB84v05681@dcave.digsys.bg> (raw)
In-Reply-To: <F1FE4396-A3FE-11D8-9A93-000A95A9B750@stowe.co.za>

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 <paul@tuckfield.com>
 > > 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





view thread (25+ messages)  latest in thread

Message-ID: <200405121108.i4CB84v05681@dcave.digsys.bg>
Permalink:  ../200405121108.i4CB84v05681@dcave.digsys.bg/
Also on:    postgresql.org/message-id/200405121108.i4CB84v05681@dcave.digsys.bg

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: daniel@digsys.bg, hal@stowe.co.za
  Subject: Re: [PERFORM] Quad processor options
  In-Reply-To: <200405121108.i4CB84v05681@dcave.digsys.bg>
  References: <F1FE4396-A3FE-11D8-9A93-000A95A9B750@stowe.co.za> <200405121108.i4CB84v05681@dcave.digsys.bg>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox