From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] O_DIRECT for WAL writes |
Date: | 2005-06-22 19:50:04 |
Message-ID: | 20689.1119469804@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Unfortunately, I cannot believe these numbers --- the near equality of
>> fsync off and fsync on means there is something very wrong with the
>> measurements. What I suspect is that your ATA drives are doing write
>> caching and thus the "fsyncs" are not really waiting for I/O at all.
> I wonder whether it would make sense to have an automatic test for this
> problem. I suspect there are lots of installations out there whose admins
> don't realize that their hardware is doing this to them.
Not sure about "automatic", but a simple little test program to measure
the speed of rewriting/fsyncing a small test file would surely be a nice
thing to have.
The reason I question "automatic" is that you really want to test each
drive being used, if the system has more than one; but Postgres has no
idea what the actual hardware layout is, and so no good way to know what
needs to be tested.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-06-22 19:50:10 | Re: [HACKERS] [PATCHES] Removing Kerberos 4 |
Previous Message | Pavel Stehule | 2005-06-22 19:47:51 | Re: pl/pgsql: END verbosity |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-06-22 19:50:10 | Re: [HACKERS] [PATCHES] Removing Kerberos 4 |
Previous Message | Pavel Stehule | 2005-06-22 19:47:51 | Re: pl/pgsql: END verbosity |