pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
To: Sean Chittenden <sean@chittenden.org>
Cc: Vivek Khera <khera@kcilink.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: go for a script! / ex:  PostgreSQL vs. MySQL
Date: Fri, 10 Oct 2003 21:55:34 -0400
Message-ID: <1065837333.12875.1.camel@jester> (raw)
In-Reply-To: <20031010225924.GC8664@perrin.nxad.com>
References: <007901c38f2b$0b585590$2802a8c0@webbased10>
	<200310101034.52073.josh@agliodbs.com>
	<3F86F5BB.90605@chuckie.co.uk>
	<x7wubcon3h.fsf@yertle.int.kciLink.com>
	<20031010225924.GC8664@perrin.nxad.com>

On Fri, 2003-10-10 at 18:59, Sean Chittenden wrote:
> > NB> So far:
> > 
> > NB> shared_buffers = 1/16th of total memory
> > NB> effective_cache_size = 80% of the supposed kernel cache.
> > 
> > Please take into account the blocksize compiled into PG, too...
> 
> Would anyone object to a patch that exports the blocksize via a
> readonly GUC?  Too many tunables are page dependant, which is
> infuriating when copying configs from DB to DB.  I wish pgsql had some
> notion of percentages for values that end with a '%'.

Rather than showing the block size, how about we change the tunables to
be physical sizes rather than block based?

        effective_cache_size = 1.5GB
        shared_buffers = 25MB

Percentages would be slick as well, but doing the above should fix most
of the issue -- and be friendlier to read.

Attachments:

  signature.asc (application/pgp-signature, 186B) download

view thread (42+ messages)  latest in thread

Message-ID: <1065837333.12875.1.camel@jester>
Permalink:  ../1065837333.12875.1.camel@jester/
Also on:    postgresql.org/message-id/1065837333.12875.1.camel@jester

 · 

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: rbt@rbt.ca, sean@chittenden.org, khera@kcilink.com
  Subject: Re: go for a script! / ex:  PostgreSQL vs. MySQL
  In-Reply-To: <1065837333.12875.1.camel@jester>

* 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