pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guy Thornley <guy@esphion.com>
To: Markus Schaber <schabi@logix-tt.com>
Cc: Luke Lonergan <llonergan@greenplum.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Large tables (was: RAID 0 not as fast as
Date: Fri, 22 Sep 2006 14:52:09 +1200
Message-ID: <20060922025209.GO6211@esphion.com> (raw)
In-Reply-To: <45123FC0.9060100@logix-tt.com>
References: <C1372993.2361%llonergan@greenplum.com>
	<45123FC0.9060100@logix-tt.com>

> >> I thought that posix_fadvise() with POSIX_FADV_WILLNEED was exactly
> >> meant for this purpose?
> > 
> > This is a good idea - I wasn't aware that this was possible.
> 
> This possibility was the reason for me to propose it. :-)

posix_fadvise() features in the TODO list already; I'm not sure if any work
on it has been done for pg8.2.

Anyway, I understand that POSIX_FADV_DONTNEED on a linux 2.6 kernel allows
pages to be discarded from memory earlier than usual. This is useful, since
it means you can prevent your seqscan from nuking the OS cache.

Of course you could argue the OS should be able to detect this, and prevent
it occuring anyway. I don't know anything about linux's behaviour in this
area.

.Guy



view thread (24+ messages)  latest in thread

Message-ID: <20060922025209.GO6211@esphion.com>
Permalink:  ../20060922025209.GO6211@esphion.com/
Also on:    postgresql.org/message-id/20060922025209.GO6211@esphion.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: guy@esphion.com, schabi@logix-tt.com, llonergan@greenplum.com
  Subject: Re: Large tables (was: RAID 0 not as fast as
  In-Reply-To: <20060922025209.GO6211@esphion.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