Re: reducing isolation tests runtime - Mailing list pgsql-hackers

From Robert Haas
Subject Re: reducing isolation tests runtime
Date
Msg-id CA+Tgmoa6usOcK77OJyT-ZnT_zcb-Ttgg--_U=pz1s+-yBr-nEg@mail.gmail.com
Whole thread Raw
In response to reducing isolation tests runtime  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: reducing isolation tests runtime
List pgsql-hackers
On Wed, Jan 24, 2018 at 6:10 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> 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
> conflict.)

Oh, cool.  Yes, the time the isolation tests take to run is quite
annoying.  I didn't realize it would be so easy to run it in parallel.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpgsql function startup-time improvements
Next
From: Tom Lane
Date:
Subject: Re: CONSTANT/NOT NULL/initializer properties for plpgsql record variables