| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Why do pg_upgrade's test use the serial schedule? |
| Date: | 2018-11-05 21:00:39 |
| Message-ID: | 20181105210039.hh4vvi4vwoq5ba2q@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
The test I'm most commonly waiting for when doing a parallel make check
is pg_upgrade. And to a significant degree that's because it uses the
serial installcheck rather than installcheck-parallel.
Is there a reason to not use installcheck-parallel?
serial:
19.42user 7.77system 1:53.23elapsed 24%CPU (0avgtext+0avgdata 111420maxresident)k
parallel:
20.76user 7.72system 1:27.05elapsed 32%CPU (0avgtext+0avgdata 112300maxresident)k
So, a saving of ~25s.
ISTM we also should disable fsyncs for the postmaster instances. Wins
another ~5s on my laptop, and I suspect it makes a larger difference on
some of the buildfarm animals.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-11-05 21:01:59 | Re: First-draft release notes for back-branch releases |
| Previous Message | David Fetter | 2018-11-05 20:53:08 | Re: settings to control SSL/TLS protocol version |