| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A test for replay of regression tests |
| Date: | 2022-01-27 21:41:21 |
| Message-ID: | CA+hUKGKV+vgpSAfQpEoSLjRG=TPzBeCXtMVBHmMBOCtc=yY8Qg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 28, 2022 at 9:27 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I have noticed on a different setup that this test adds 11 minutes to
> the runtime of the recovery tests, effectively doubling it. The doubling
> is roughly true on faster setups, too. At least I would like a simple
> way to disable the test.
Ouch, that's ... a lot. Some randomly selected times: ~20 seconds
(dev machines), ~40 seconds (Cirrus CI's Windows image), ~2-3 minutes
(very cheap cloud host accounts), ~3 minutes (my Rapsberry Pi pinned
onto two CPU cores), ~11 minutes (your Windows number). It would be
good to understand why that's such an outlier.
Re skipping, I've also been wondering about an exclusion list to skip
parts of the regression tests that don't really add recovery coverage
but take non-trivial time, like the join tests.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-01-27 21:58:27 | Re: Write visibility map during CLUSTER/VACUUM FULL |
| Previous Message | Andres Freund | 2022-01-27 21:15:18 | Re: Design of pg_stat_subscription_workers vs pgstats |