From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: seq scan cache vs. index cache smackdown
Date: Tue, 15 Feb 2005 14:04:49 -0500
Message-ID: <m3hdkdod9q.fsf@knuth.knuth.cbbrowne.com> (raw)
References: <6EE64EF3AB31D5448D0007DD34EEB3412A761E@Herge.rcsinc.local>
In the last exciting episode, merlin.moncure@rcsonline.com ("Merlin Moncure") wrote:
>> It seems inevitable that Postgres will eventually eliminate that
>> redundant layer of buffering. Since mmap is not workable, that
>> means using O_DIRECT to read table and index data.
>
> What about going the other way and simply letting the o/s do all the
> caching? How bad (or good) would the performance really be?
I'm going to see about taking this story to OLS (Ottawa Linux
Symposium) in July and will see what hearing I can get. There are
historically some commonalities in the way this situation is regarded,
in that there was _long_ opposition to the notion of having unbuffered
disk devices.
If there's more "story" that definitely needs to be taken, let me
know...
--
output = reverse("moc.enworbbc" "@" "enworbbc")
http://linuxdatabases.info/info/slony.html
Rules of the Evil Overlord #90. "I will not design my Main Control
Room so that every workstation is facing away from the door."
<http://www.eviloverlord.com/;
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: cbbrowne@acm.org
Subject: Re: seq scan cache vs. index cache smackdown
In-Reply-To: <m3hdkdod9q.fsf@knuth.knuth.cbbrowne.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