pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Paul Thomas <paul@tmsl.demon.co.uk>
To: pgsql-performance @ postgresql . org <pgsql-performance@postgresql.org>
Subject: Re: go for a script! / ex:  PostgreSQL vs. MySQL
Date: Thu, 9 Oct 2003 11:12:55 +0100
Message-ID: <20031009111255.A17336@bacon> (raw)
In-Reply-To: <B7397E6AC70AB1418180FA3480B9365556A69A@deun2kex01.realgarant.de>
References: <B7397E6AC70AB1418180FA3480B9365556A69A@deun2kex01.realgarant.de>


On 09/10/2003 09:29 Oliver Scheit wrote:
> Hi guys,
> 
> I followed the discussion and here are my 0.2$:
> 
> I think instead of thinking about where to put the
> information about tuning, someone should provide a
> "pgsql-autotune". Maybe even a shell script would do the
> trick.
> 
> It's not so hard to find out, how much memory is installed,
> and IMHO SHARED_BUFFERS, SORT_MEM and EFFECTIVE_CACHE_SIZE
> depend heavily on this. a "cat /proc/sys/kernel/shmmax"
> would give some valuable information on linux boxes,
> there is probably other stuff for different OSes.
> 
> random_page_cost could be set after probing the harddisks,
> maybe even do a hdparm -tT if they seem to be ATA, not SCSI.
> 
> Now, let's pretend the script finds out there is 1 GB RAM,
> it could ask something like "Do you want to optimize the
> settings for postgres (other applications may suffer from
> having not enough RAM) or do you want to use moderate
> settings?"
> 
> Something like this, you get the idea.


ISR reading that 7.4 will use a default of shared_beffers = 1000 if the 
machine can support it (most can). This alone should make a big difference 
in out-of-the-box performance.

-- 
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller 
Business |
| Computer Consultants         | 
http://www.thomas-micro-systems-ltd.co.uk   |
+------------------------------+---------------------------------------------+



view thread (42+ messages)  latest in thread

Message-ID: <20031009111255.A17336@bacon>
Permalink:  ../20031009111255.A17336@bacon/
Also on:    postgresql.org/message-id/20031009111255.A17336@bacon

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: paul@tmsl.demon.co.uk
  Subject: Re: go for a script! / ex:  PostgreSQL vs. MySQL
  In-Reply-To: <20031009111255.A17336@bacon>

* 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