Re: fsync, fdatasync, open_sync, and open_datasync, --

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql(at)mohawksoft(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: fsync, fdatasync, open_sync, and open_datasync, --
Date: 2004-08-11 17:53:12
Message-ID: 411A5D08.1020409@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
>
>>Tom Lane wrote:
>>
>>>I don't think any test that we could build would be as useful as simply
>>>trying the different settings with an installation's real workload.
>
>
>>Benchmarking the real workload isn't always so easy, and might be quite
>>time consuming to obtain meaningful values.
>
>
> The concern was about whether people might be missing an easy speedup of
> 2x or more. I don't think it'd be that hard to tell ;-) if one setting
> is an order of magnitude better than another for your workload. If
> there's not an obvious difference then you haven't wasted much effort
> checking.

This is probably more obvious with a 100 % write test app, compared to
5-10 % write as in average apps. Those 90% reading will make your
benchmarking unreliable unless you have it running for a longer period
to get a better statistic. Improving signal/noise ratio (i.e. avoiding
reads) makes it simpler.

Regards,
Andreas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2004-08-11 18:37:06 Re: Add Missing From?
Previous Message Tom Lane 2004-08-11 17:33:18 Re: pg_restore (libpq? parser?) bug in 8