From: Neil Conway <neilc@samurai.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Curt Sampson <cjs@cynic.net>
Cc: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres 7.3.1 poor insert/update/search performance
Date: 02 Feb 2003 12:01:41 -0500
Message-ID: <1044205301.760.103.camel@tokyo> (raw)
In-Reply-To: <200302021039.h12Adah03315@candle.pha.pa.us>
References: <200302021039.h12Adah03315@candle.pha.pa.us>
On Sun, 2003-02-02 at 05:39, Bruce Momjian wrote:
> We need free-behind for large sequential scans, like Solaris has. Do we
> have LRU-2 or LRU-K now?
No.
> As I remember, DIRECT doesn't return until the data hits the disk
> (because there is no OS cache), so if you want to write a page so you
> can reused the buffer, DIRECT would be quite slow.
Why? If there is a finite amount of memory for doing buffering, the data
needs to be written to disk at *some* point, anyway. And if we didn't
use the OS cache, the size of the PostgreSQL shared buffer would be much
larger (I'd think 80% or more of the physical RAM in a typical high-end
machine, for dedicated PostgreSQL usage).
One possible problem would be the fact that it might mean that writing
out dirty pages would become part of some key code paths in PostgreSQL
(rather than assuming that the OS can write out dirty pages in the
background, as it chooses to). But there are lots of ways to work around
this, notably by using a daemon to periodically write out some of the
pages in the background.
Cheers,
Neil
--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
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: neilc@samurai.com, pgman@candle.pha.pa.us, cjs@cynic.net, andrew@libertyrms.info
Subject: Re: Postgres 7.3.1 poor insert/update/search performance
In-Reply-To: <1044205301.760.103.camel@tokyo>
References: <200302021039.h12Adah03315@candle.pha.pa.us> <1044205301.760.103.camel@tokyo>
* 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