| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, "Bernd Helmle" <mailings(at)oopsware(dot)de> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: no universally correct setting for fsync |
| Date: | 2010-05-10 20:59:34 |
| Message-ID: | 4BE82D6602000025000314D6@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Cédric Villemain<cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
> On a recent pg_restore -j 32, with perc 6i with BBU, RAID10 8 hd,
> results were not so bas with fsync turn on. (XFS with nobarrier su
> and sw)
> -- deactivate fsync
> time pg_restore -U postgres -d foodb -j 32 foo.psql
> real 170m0.527s
> user 43m12.914s
> sys 1m56.499s
> -- activate fsync
> time pg_restore -U postgres -d foodb -j 32 foo.psql
> real 177m0.121s
> user 42m54.581s
> sys 2m0.452s
Wow. In a situation where you save seven minutes (4%), it's hardly
worth turning off.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-05-10 21:20:18 | Re: no universally correct setting for fsync |
| Previous Message | Josh Berkus | 2010-05-10 20:35:32 | Re: no universally correct setting for fsync |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-05-10 21:20:18 | Re: no universally correct setting for fsync |
| Previous Message | Josh Berkus | 2010-05-10 20:42:21 | Re: max_standby_delay considered harmful |