reducing isolation tests runtime

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

On the subject of test total time, we could paralelize isolation tests.
Right now "make check" in src/test/isolation takes 1:16 on my machine.
Test "timeouts" takes full 40s of that, with nothing running in parallel
-- the machine is completely idle.

Seems like we can have a lot of time back just by changing the schedule
to use multiple tests per line (in particular, put the other slow tests
together with timeouts), per the attached; with this new schedule,
isolation takes 44 seconds in my machine -- a win of 32 seconds. We can
win a couple of additional second by grouping a few other lines, but
this is the biggest win.

(This needs to be adjusted because some table names in the specs

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
isosched.patch text/plain 1.9 KB

In response to


Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2018-01-24 23:30:20 Re: reducing isolation tests runtime
Previous Message Robert Haas 2018-01-24 21:39:44 pgsql: Avoid referencing off the end of subplan_partition_offsets.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-01-24 23:16:24 Re: plpgsql function startup-time improvements
Previous Message Stephen Frost 2018-01-24 22:56:41 Re: Possible performance regression with pg_dump of a large number of relations