From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Trouble with hashagg spill I/O pattern and costing |
Date: | 2020-05-21 18:54:59 |
Message-ID: | 20200521185459.wrspycddukcztlgi@development |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 21, 2020 at 08:34:05PM +0200, Tomas Vondra wrote:
>On Thu, May 21, 2020 at 11:19:01AM -0700, Jeff Davis wrote:
>
> ...
>
>I think we should do the pre-allocation patch too. I haven't tried yet
>but I believe the tlist fix alone won't do nearly as good.
>
I've done some measurements on the smaller (SSD) machine, and the
comparison looks like this:
sort hash hash+prealloc+tlist hash+tlist
--------------------------------------------------------
4MB 331 478 188 330
128MB 222 434 210 350
The last column is master with the tlist tweak alone - it's better than
hashagg on master alone, but it's not nearly as good as with both tlist
and prealloc patches.
I can't test this on the larger box with SATA temporary tablespace at
the moment (other tests are running), but I believe the difference will
be even more pronounced there.
I don't think we're under a lot of pressure - beta1 is out anyway, so we
have time to do proper testing first.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2020-05-21 19:04:19 | Re: Trouble with hashagg spill I/O pattern and costing |
Previous Message | Tomas Vondra | 2020-05-21 18:34:05 | Re: Trouble with hashagg spill I/O pattern and costing |