|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Robert Haas <robertmhaas(at)gmail(dot)com>|
|Cc:||Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: pgsql: Add parallel-aware hash joins.|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> There is no need to collect years of data in order to tell whether or
> not the time to run the tests has increased by as much on developer
> machines as it has on prairiedog. You showed the time going from 3:36
> to 8:09 between 2014 and the present. That is a 2.26x increase. It
> is obvious from the numbers I posted before that no such increase has
> taken place in the time it takes to run 'make check' on my relatively
> modern laptop. Whatever difference exists is measured in
I may be wasting my breath here, but in one more attempt to convince
you that "time make check" on your laptop is not the only number that
anyone should be interested in, here are some timings off my development
workstation. These are timings off current tip of each release branch,
all the same build options etc, so very comparable:
[ don't remember the equivalent to top-level make temp-install here ]
top-level make check 24.725s
make temp-install 3.702s
top-level make check 24.709s
make temp-install 3.971s
top-level make check 24.048s
make temp-install 4.051s
top-level make check 21.784s
make temp-install 4.048s
top-level make check 24.027s
I copied-and-pasted the "real time" results of time(1) for each of these,
not bothering to round them off; but the numbers are only reproducible
to half a second or so, so there's no significance in the last couple
digits. Most numbers above are the minimum of 2 or more runs.
What I take away here is that there's been a pretty steep cost increase
for the regression tests since v10, and that is *not* in line with the
historical average. In fact, in most years we've bought enough speedup
through performance improvements to pay for the test cases we added.
This is masked if you just eyeball "make check" compared to several years
ago. But to do that, you have to ignore the fact that we made substantial
improvements in the runtime of initdb as well as the regression tests
proper circa v10, and we've now thrown that away and more.
So I remain dissatisfied with these results, particularly because in
my own work habits, the time for "make installcheck-parallel" is way
more interesting than "make check". I avoid redoing installs and
initdbs if I don't need them.
> ... Even if that meant that you had
> to wait 1 extra second every time you run 'make check', I would judge
> that worthwhile.
I think this is a bad way of looking at it. Sure, in terms of
one developer doing one test run, a second or two means nothing.
But for instance, if you want to do 100 test runs in hope of catching
a seldom-reproduced bug, it adds up. It also adds up when you consider
the aggregate effort expended by the buildfarm, or the time you have
to wait to see buildfarm results.
> Another thing you could do is consider applying the patch Thomas
> already posted to reduce the size of the tables involved.
Yeah. What I thought this argument was about was convincing *you*
that that would be a reasonable patch to apply. It seems from my
experiment on gaur that that patch makes the results unstable, so
if we can do it at all it will need more work. But I do think
it's worth putting in some more sweat here. In the long run the
time savings will add up.
regards, tom lane
|Next Message||Robert Haas||2018-01-25 04:39:26||Re: pgsql: Add parallel-aware hash joins.|
|Previous Message||Tom Lane||2018-01-24 23:46:59||Re: reducing isolation tests runtime|
|Next Message||Tom Lane||2018-01-25 04:17:38||Re: Further cleanup of pg_dump/pg_restore item selection code|
|Previous Message||David G. Johnston||2018-01-25 03:36:05||Further cleanup of pg_dump/pg_restore item selection code|