Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime
Date: 2021-05-11 14:07:43
Message-ID: 3c2303a8-c414-55a3-0b0a-294d81b7b98c@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-05-11 14:07:44 Re: Performance degradation of REFRESH MATERIALIZED VIEW
Previous Message Tomas Vondra 2021-05-11 13:58:20 Re: Performance degradation of REFRESH MATERIALIZED VIEW