Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime
Date
Msg-id 3c2303a8-c414-55a3-0b0a-294d81b7b98c@dunslane.net
Whole thread Raw
In response to Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5/10/21 2:03 AM, Tom Lane wrote:
> I noted that, while privileges.sql doesn't stand out in terms of
> runtime normally (it's only the fourth slowest test in its
> parallel group), it looks absolutely horrid in CLOBBER_CACHE_ALWAYS
> testing.  On hyrax's latest run, it takes nearly 9000 seconds longer
> than the next-slowest member of its group.  Remembering that the
> core regression tests are run thrice in a minimal buildfarm cycle,
> this test is single-handedly responsible for over seven hours of the
> 54 hour total build cycle.


FWIW, I would normally suggest a CCA enabled animal disable some of the
tests so that it doesn't run the core tests thrice. The easiest way to
do that is: --skip-steps='check pg_upgrade-check'


Even so your point is well taken.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Performance degradation of REFRESH MATERIALIZED VIEW
Next
From: Tomas Vondra
Date:
Subject: Re: Performance degradation of REFRESH MATERIALIZED VIEW