Re: Hash index build performance tweak from sorting

From: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
To: David Zhang <david(dot)zhang(at)highgo(dot)ca>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hash index build performance tweak from sorting
Date: 2022-08-30 16:27:04
Message-ID: CANbhV-ENo3y+BqJRyjE303QfUYyoASn5A+65FZh56-v6+H-3Mg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 5 Aug 2022 at 20:46, David Zhang <david(dot)zhang(at)highgo(dot)ca> wrote:
>
> On 2022-08-01 8:37 a.m., Simon Riggs wrote:
> > Using the above test case, I'm getting a further 4-7% improvement on
> > already committed code with the attached patch, which follows your
> > proposal.
>
> I ran two test cases: for committed patch `hash_sort_by_hash.v3.patch`, I can see about 6 ~ 7% improvement; and after applied patch `hash_inserted_sorted.v2.patch`, I see about ~3% improvement. All the test results are based on 10 times average on two different machines.

Thanks for testing David.

It's a shame you only see 3%, but that's still worth it.

--
Simon Riggs http://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-08-30 16:30:48 Re: archive modules
Previous Message Tom Lane 2022-08-30 16:17:33 Re: Reducing the chunk header sizes on all memory context types