| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TAP test breakage on MacOS X |
| Date: | 2014-10-31 06:03:09 |
| Message-ID: | 20982.1414735389@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> writes:
> On Thu, Oct 30, 2014 at 10:49:33PM -0400, Tom Lane wrote:
>> I think the installs as such aren't the only reason for the sucky
>> performance. We need to also reduce the number of initdb cycles incurred
>> by the TAP tests. It's useless for example that the pg_controldata test
>> creates its very own $PGDATA rather than sharing one with other tests.
> One could memoize initdb within the suite. Call it once per distinct command
> line, caching the resulting data directory. Copy the cached data directory
> for each test desiring one.
At least on older/slower machines like prairiedog, even having to copy
$PGDATA for each test is unappealing. Some numbers for reference:
make install 22 sec
initdb 76 sec
initdb -N 33 sec
cp -r $PGDATA /tmp 17 sec
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-10-31 06:41:46 | Re: tracking commit timestamps |
| Previous Message | Michael Paquier | 2014-10-31 05:55:11 | Re: tracking commit timestamps |