pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <andrew@libertyrms.info>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: 7.3.1 New install, large queries are slow
Date: Sat, 18 Jan 2003 11:24:26 -0500
Message-ID: <20030118112426.A23790@mail.libertyrms.com> (raw)
In-Reply-To: <21623.1042865371@sss.pgh.pa.us>
References: <Pine.BSF.4.44.0301171336180.56567-100000@torgo.978.org>
	<21623.1042865371@sss.pgh.pa.us>

On Fri, Jan 17, 2003 at 11:49:31PM -0500, Tom Lane wrote:
> Jeff <threshar@torgo.978.org> writes:
> > Informix, oracle, etc all do raw device access bypassing the kernels
> > buffering, etc.  So they need heaping gobules of memory to do the same
> > thing the kernel does..
> 
> D'oh, I believe Jeff's put his finger on it.  You need lotsa RAM if you
> are trying to bypass the OS.  But Postgres would like to work with the
> OS, not bypass it.

One of the interesting things I have been playing with on Solaris
recently is the various no-buffer settings you can give to the kernel
for filesystems.  The idea is that you don't have the kernel do the
buffering, and you set your database's shared memory setting
_reeeeal_ high.  

As nearly as I can tell, there is again no benefit with PostgreSQL. 
I'd also be amazed if this approach is a win for other systems.  But
a lot of DBAs seem to believe that they know better than their
computers which tables are "really" accessed frequently.  I think
they must be smarter than I am: I'd rather trust a system that was
designed to track these things and change the tuning on the fly,
myself.

(To be fair, there are some cases where you have an
infrequently-accessed table which nevertheless is required to be fast
for some reason or other, so you might want to force it to stay in
memory.)

A

----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110




view thread (66+ messages)  latest in thread

Message-ID: <20030118112426.A23790@mail.libertyrms.com>
Permalink:  ../20030118112426.A23790@mail.libertyrms.com/
Also on:    postgresql.org/message-id/20030118112426.A23790@mail.libertyrms.com

 · 

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-performance@postgresql.org
  Cc: andrew@libertyrms.info
  Subject: Re: 7.3.1 New install, large queries are slow
  In-Reply-To: <20030118112426.A23790@mail.libertyrms.com>
  References: <Pine.BSF.4.44.0301171336180.56567-100000@torgo.978.org> <21623.1042865371@sss.pgh.pa.us> <20030118112426.A23790@mail.libertyrms.com>

* 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