Re: Horrible CREATE DATABASE Performance in High Sierra
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Brent Dearth <brent.dearth@gmail.com>, pgsql-hackers@postgresql.org
Date: 2017-10-02T19:54:43Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2017-10-02 15:42:25 -0400, Tom Lane wrote: >> I experimented with this further by seeing whether the msync() code path >> is of any value on Sierra either. The answer seems to be "no": cloning >> a scale-1000 pgbench database takes about 17-18 seconds on my Sierra >> laptop using unmodified HEAD, but if I dike out the msync() logic then >> it takes 16-17 seconds. Both numbers jump around a little, but using >> msync is strictly worse. > Well, that's only measuring one type of workload. Could you run a normal > pgbench with -P1 or so for 2-3 checkpoint cycles and see how big the > latency differences are? Should I expect there to be any difference at all? We don't enable *_flush_after by default on non-Linux platforms. regards, tom lane
Commits
-
Increase distance between flush requests during bulk file copies.
- c3723317d08c 10.1 landed
- 643c27e36ff3 11.0 landed
- 13a8924ecf00 9.6.6 landed