Re: reducing isolation tests runtime

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: reducing isolation tests runtime
Date: 2019-02-13 18:01:52
Message-ID: 30746.1550080912@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Right, but why don't we allow for more tests in a group, and then use a
> default max_connections to limit concurrency? Having larger groups is
> advantageous wrt test runtime - it reduces the number of artificial
> serialization point where the slowest test slows things down. Obviously
> there's still a few groups that are needed for test interdependency
> management, but that's comparatively rare. We have have plenty groups
> that are just broken up to stay below max_concurrent_tests.

Meh. That would also greatly increase the scope for hard-to-reproduce
conflicts between concurrent tests. I'm not especially excited about
going there.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-02-13 19:16:37 pgsql: Add basic support for using the POPCNT and SSE4.2s LZCNT opcodes
Previous Message Andres Freund 2019-02-13 17:46:50 Re: reducing isolation tests runtime

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-02-13 18:12:25 Re: subscriptionCheck failures on nightjar
Previous Message Tom Lane 2019-02-13 17:59:19 Re: subscriptionCheck failures on nightjar