pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: markw@osdl.org
To: manfred@colorfullife.com
Cc: tgl@sss.pgh.pa.us
Cc: josh@agliodbs.com
Cc: Q@ping.be
Cc: pgman@candle.pha.pa.us
Cc: markir@paradise.net.nz
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
Date: Thu, 25 Mar 2004 09:16:40 -0800 (PST)
Message-ID: <200403251716.i2PHGh222327@mail.osdl.org> (raw)
In-Reply-To: <40627A6F.9010202@colorfullife.com>

On 25 Mar, Manfred Spraul wrote:
> Tom Lane wrote:
> 
>>markw@osdl.org writes:
>>  
>>
>>>I could certainly do some testing if you want to see how DBT-2 does.
>>>Just tell me what to do. ;)
>>>    
>>>
>>
>>Just do some runs that are identical except for the wal_sync_method
>>setting.  Note that this should not have any impact on SELECT
>>performance, only insert/update/delete performance.
>>  
>>
> I've made a test run that compares fsync and fdatasync: The performance 
> was identical:
> - with fdatasync:
> 
> http://khack.osdl.org/stp/290607/
> 
> - with fsync:
> http://khack.osdl.org/stp/290483/
> 
> I don't understand why. Mark - is there a battery backed write cache in 
> the raid controller, or something similar that might skew the results? 
> The test generates quite a lot of wal traffic - around 1.5 MB/sec. 
> Perhaps the writes are so large that the added overhead of syncing the 
> inode is not noticable?
> Is the pg_xlog directory on a seperate drive?
> 
> Btw, it's possible to request such tests through the web-interface, see
> http://www.osdl.org/lab_activities/kernel_testing/stp/script_param.html

We have 2 Adaptec 2200s controllers, without the battery backed add-on,
connected to four 10-disk arrays in those systems.  I can't think of
anything off hand that would skew the results.

The pg_xlog directory is not on a separate drive.  I haven't found the
best way to lay out of the drives on those systems yet, so I just have
everything on a 28 drive lvm2 volume.

Mark



view thread (42+ messages)  latest in thread

Message-ID: <200403251716.i2PHGh222327@mail.osdl.org>
Permalink:  ../200403251716.i2PHGh222327@mail.osdl.org/
Also on:    postgresql.org/message-id/200403251716.i2PHGh222327@mail.osdl.org

 · 

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: markw@osdl.org, manfred@colorfullife.com, tgl@sss.pgh.pa.us, josh@agliodbs.com, Q@ping.be, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] fsync method checking
  In-Reply-To: <200403251716.i2PHGh222327@mail.osdl.org>

* 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