Re: Change GUC hashtable to use simplehash? - Mailing list pgsql-hackers

From Junwang Zhao
Subject Re: Change GUC hashtable to use simplehash?
Date
Msg-id CAEG8a3KnwqopxjHSm0rVy4jBKhOw7_25VWp0Gq6FDSdiqKOb=g@mail.gmail.com
Whole thread Raw
In response to Re: Change GUC hashtable to use simplehash?  (John Naylor <johncnaylorls@gmail.com>)
Responses Re: Change GUC hashtable to use simplehash?
List pgsql-hackers
Hi John,

On Mon, Jan 8, 2024 at 10:44 AM John Naylor <johncnaylorls@gmail.com> wrote:
>
> On Sat, Jan 6, 2024 at 9:01 AM jian he <jian.universality@gmail.com> wrote:
> >
> > latency average = 147.782 ms
> > select * from bench_cstring_hash_unaligned(100000);
> > latency average = 101.179 ms
> > select * from bench_cstring_hash_aligned(100000);
> > latency average = 101.219 ms
>
> Thanks for testing again! This looks closer to my results. It doesn't
> show improvement for the aligned case, but it's not worse, either.
>
> There is still some polishing to be done, mostly on comments/examples,
> but I think it's mostly there. I'll return to it by next week.
>
>

+ * Portions Copyright (c) 2018-2023, PostgreSQL Global Development Group

A kind reminder, it's already 2024 :)

I'm also curious why the 2018, is there any convention for that?

--
Regards
Junwang Zhao



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Documentation to upgrade logical replication cluster
Next
From: Peter Eisentraut
Date:
Subject: Escape output of pg_amcheck test