From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: reducing isolation tests runtime |
Date: | 2018-01-24 23:30:20 |
Message-ID: | CA+Tgmoa6usOcK77OJyT-ZnT_zcb-Ttgg--_U=pz1s+-yBr-nEg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 24, 2018 at 6:10 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-01-24 23:35:00 | Re: reducing isolation tests runtime |
Previous Message | Alvaro Herrera | 2018-01-24 23:10:06 | reducing isolation tests runtime |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-01-24 23:32:40 | Re: CONSTANT/NOT NULL/initializer properties for plpgsql record variables |
Previous Message | Tom Lane | 2018-01-24 23:16:24 | Re: plpgsql function startup-time improvements |