pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ang Chin Han <angch@bytecraft.com.my>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: further testing on IDE drives
Date: Wed, 15 Oct 2003 18:25:19 +0800
Message-ID: <3F8D208F.2020702@bytecraft.com.my> (raw)
In-Reply-To: <200310101724.h9AHOTs24892@candle.pha.pa.us>
References: <200310101724.h9AHOTs24892@candle.pha.pa.us>

Bruce Momjian wrote:

> Yes.  If you were doing multiple WAL writes before transaction fsync,
> you would be fsyncing every write, rather than doing two writes and
> fsync'ing them both.  I wonder if larger transactions would find
> open_sync slower?

No hard numbers, but I remember testing fsync vs open_sync something ago 
on 7.3.x.

open_sync was blazingly fast for pgbench, but for when we switched our 
development database over to open_sync, things slowed to a crawl.

This was some months ago, and I might be wrong, so take it with a grain 
of salt. It was on Red Hat 8's Linux kernel 2.4.18, I think. YMMV.

Will be testing it real soon tonight, if possible.

view thread (18+ messages)

Message-ID: <3F8D208F.2020702@bytecraft.com.my>
Permalink:  ../3F8D208F.2020702@bytecraft.com.my/
Also on:    postgresql.org/message-id/3F8D208F.2020702@bytecraft.com.my

 · 

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: angch@bytecraft.com.my, pgman@candle.pha.pa.us, scott.marlowe@ihs.com
  Subject: Re: further testing on IDE drives
  In-Reply-To: <3F8D208F.2020702@bytecraft.com.my>

* 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