Re: reducing isolation tests runtime

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: reducing isolation tests runtime
Date: 2018-01-25 20:58:04
Message-ID: 29555.1516913884@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Here's a concrete proposal. Runtime is 45.7 seconds on my laptop. It
> can be further reduced, but not by more than a second or two unless you
> get in the business of modifying other tests. (I only modified
> deadlock-soft-2 because it saves 5 seconds).

Looks reasonable to me, but do we want to set any particular convention
about the max number of tests to run in parallel? If so there should
be at least a comment saying what.

> Admittedly the new isolation_schedule file is a bit ugly.

Meh, seems fine.

We won't know if this really works till it hits the buildfarm,
I suppose.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2018-01-25 21:27:28 Re: reducing isolation tests runtime
Previous Message Alvaro Herrera 2018-01-25 20:34:15 Re: reducing isolation tests runtime

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-01-25 21:21:14 Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
Previous Message Stephen Frost 2018-01-25 20:52:57 Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump