From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: win32 performance - fsync question |
Date: | 2005-02-17 23:41:54 |
Message-ID: | 42152BC2.40400@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark wrote:
> Oliver Jowett <oliver(at)opencloud(dot)com> writes:
>
>
>>So Linux is indeed doing a cache flush on fsync
>
>
> Actually I think the root of the problem was precisely that Linux does not
> issue any sort of cache flush commands to drives on fsync. There was some talk
> on linux-kernel of what how they could take advantage of new ATA features
> planned on new SATA drives coming out now to solve this. But they didn't seem
> to think it was urgent or worth the performance hit of doing a complete cache
> flush.
Oh, ok. I haven't really kept up to date with it; I just run with
write-cache disabled on my IDE drives as a matter of course.
I did see this:
http://www.ussg.iu.edu/hypermail/linux/kernel/0304.1/0471.html
which implies you're never going to get an implementation that is safe
across all IDE hardware :(
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Evgeny Rodichev | 2005-02-17 23:56:02 | Re: win32 performance - fsync question |
Previous Message | Greg Stark | 2005-02-17 22:14:24 | Re: win32 performance - fsync question |