pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Date: Sat, 03 Jul 2021 18:59:49 -0400
Message-ID: <1289102.1625353189@sss.pgh.pa.us> (raw)
In-Reply-To: <702694.1625159862@sss.pgh.pa.us>
References: <1582507.1624227029@sss.pgh.pa.us>
	<467e9f1a-f440-4875-2677-36f52f556f62@dunslane.net>
	<1799344.1624396289@sss.pgh.pa.us>
	<3f3f3d9d-fccf-318d-5c16-622778b42645@dunslane.net>
	<693603.1625151671@sss.pgh.pa.us>
	<ed2e8c7f-dbfc-29a5-1c89-2dd2bd5075ea@dunslane.net>
	<702694.1625159862@sss.pgh.pa.us>

I wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> Seems reasonable. I don't have a CCA animal any more, but I guess I
>> could set up a test.

> I can run a test here --- I'll commandeer sifaka for awhile,
> since that's the fastest animal I have.

Done, and here's the results:

Traditional way (-DCLOBBER_CACHE_ALWAYS): 32:53:24
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2021-07-01%2018%3A06%3A09

New way: 16:15:43
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2021-07-03%2004%3A02%3A16

That's running sifaka's full test schedule including TAP tests,
which ordinarily takes it a shade under 10 minutes.  The savings
on a non-TAP run would be a lot less, of course, thanks to
fewer initdb invocations.

Although I lacked the patience to run a full back-branch cycle
with -DCLOBBER_CACHE_ALWAYS, I did verify that the patch
correctly injects that #define when running an old branch.
So I think it's ready to go into the buildfarm, modulo any
cosmetic work you might want to do.

			regards, tom lane





view thread (11+ messages)  latest in thread

Message-ID: <1289102.1625353189@sss.pgh.pa.us>
Permalink:  ../1289102.1625353189@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1289102.1625353189@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, peter.eisentraut@enterprisedb.com
  Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
  In-Reply-To: <1289102.1625353189@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox