Re: Disk-based hash aggregate's cost model

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Disk-based hash aggregate's cost model
Date: 2020-09-04 12:56:40
Message-ID: 20200904125640.wsk77dohvrdfu255@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 03, 2020 at 05:53:43PM -0700, Jeff Davis wrote:
>On Tue, 2020-09-01 at 23:19 +0200, Tomas Vondra wrote:
>> FWIW any thoughts about the different in temp size compared to
>> CP_SMALL_TLIST?
>
>Are you referring to results from a while ago? In this thread I don't
>see what you're referring to.
>
>I tried in a simple case on REL_13_STABLE, with and without the
>CP_SMALL_TLIST change, and I saw only a tiny difference. Do you have a
>current case that shows a larger difference?
>

I'm referring to the last charts in the message from July 27, comparing
behavior with CP_SMALL_TLIST fix vs. master (which reverted/replaced the
CP_SMALL_TLIST bit).

Those charts show that the CP_SMALL_TLIST resulted in smaller temp files
(per EXPLAIN ANALYZE the difference is ~25%) and also lower query
durations (also in the ~25% range).

I can repeat those tests, if needed.

[1] https://www.postgresql.org/message-id/20200724012248.y77rpqc73agrsvb3@development

>The only thing I can think of that might change is the size of the null
>bitmap or how fields are aligned.
>

Maybe. Not sure.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2020-09-04 13:23:37 Re: Ideas about a better API for postgres_fdw remote estimates
Previous Message Tomas Vondra 2020-09-04 12:46:19 Re: Get memory contexts of an arbitrary backend process