| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | John Hansen <john(at)geeknet(dot)com(dot)au>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bgwriter behavior |
| Date: | 2004-12-28 18:10:11 |
| Message-ID: | 1514.1104257411@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> John Hansen wrote:
>> On another note, how do you know for sure, that your drive does not lie
>> about fsync?
> I just tried and got 115tps with fsync off vs 100 with fsync on, so
> fsync is certainly doing something.
[ raised eyebrow... ] Something is wrong with that. I'd expect a
*much* higher difference. It's difficult to credit a tps rate higher
than your disk's RPM rating with fsync on, but most modern CPUs can do
a lot better than that with fsync off. If you have a 7200 RPM drive
then I'd believe the 100 figure, but not the other ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-12-28 18:22:06 | Re: Bgwriter behavior |
| Previous Message | Bruce Momjian | 2004-12-28 18:04:54 | Re: Bgwriter behavior |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-12-28 18:22:06 | Re: Bgwriter behavior |
| Previous Message | Bruce Momjian | 2004-12-28 18:04:54 | Re: Bgwriter behavior |