pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: Guy Thornley <guy@esphion.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: O_DIRECT setting
Date: Thu, 23 Sep 2004 09:35:45 -0400 (EDT)
Message-ID: <200409231335.i8NDZjR21993@candle.pha.pa.us> (raw)
In-Reply-To: <1095911914.22485.414.camel@localhost.localdomain>


TODO has:

	* Consider use of open/fcntl(O_DIRECT) to minimize OS caching

Should the item be removed?

---------------------------------------------------------------------------

Neil Conway wrote:
> On Mon, 2004-09-20 at 17:57, Guy Thornley wrote:
> > According to the manpage, O_DIRECT implies O_SYNC:
> > 
> >         File I/O is done directly to/from user space buffers.  The I/O is
> >         synchronous, i.e., at the completion of the read(2) or write(2)
> >         system call, data is guaranteed to have been transferred.
> 
> This seems like it would be a rather large net loss. PostgreSQL already
> structures writes so that the writes we need to hit disk immediately
> (WAL records) are fsync()'ed -- the kernel is given more freedom to
> schedule how other writes are flushed from the cache. Also, my
> recollection is that O_DIRECT also disables readahead -- if that's
> correct, that's not what we want either.
> 
> BTW, using O_DIRECT has been discussed a few times in the past. Have you
> checked the list archives? (for both -performance and -hackers)
> 
> > Would people be interested in a performance benchmark?
> 
> Sure -- I'd definitely be curious, although as I said I'm skeptical it's
> a win.
> 
> > I need some benchmark tips :)
> 
> Some people have noted that it can be difficult to use contrib/pgbench
> to get reproducible results -- you might want to look at Jan's TPC-W
> implementation or the OSDL database benchmarks:
> 
> http://pgfoundry.org/projects/tpc-w-php/
> http://www.osdl.org/lab_activities/kernel_testing/osdl_database_test_suite/
> 
> > Incidentally, postgres heap files suffer really, really bad fragmentation,
> > which affects sequential scan operations (VACUUM, ANALYZE, REINDEX ...)
> > quite drastically. We have in-house patches that somewhat alleiviate this,
> > but they are not release quality.
> 
> Can you elaborate on these "in-house patches"?
> 
> -Neil
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (9+ messages)  latest in thread

Message-ID: <200409231335.i8NDZjR21993@candle.pha.pa.us>
Permalink:  ../200409231335.i8NDZjR21993@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200409231335.i8NDZjR21993@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, neilc@samurai.com, guy@esphion.com
  Subject: Re: O_DIRECT setting
  In-Reply-To: <200409231335.i8NDZjR21993@candle.pha.pa.us>

* 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