From: | Amul Sul <sulamul(at)gmail(dot)com> |
---|---|
To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock |
Date: | 2023-11-08 05:09:34 |
Message-ID: | CAAJ_b96MDOxVk=DTFNq-TX448gYD-pz8e9LvaXYX5ZybF-mBQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 6, 2023 at 4:44 PM Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru>
wrote:
>
>
> > On 6 Nov 2023, at 14:31, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >
> > dynahash is notoriously slow, which is why we have simplehash.h since
> > commit b30d3ea824c5. Maybe we could use that instead.
>
> Dynahash has lock partitioning. Simplehash has not, AFAIK.
> The thing is we do not really need a hash function - pageno is already a
> best hash function itself. And we do not need to cope with collisions much
> - we can evict a collided buffer.
>
> Given this we do not need a hashtable at all. That’s exact reasoning how
> banks emerged, I started implementing dynahsh patch in April 2021 and found
> out that “banks” approach is cleaner. However the term “bank” is not common
> in software, it’s taken from hardware cache.
>
I agree that we don't need the hash function to generate hash value out of
pageno which itself is sufficient, but I don't understand how we can get
rid of
the hash table itself -- how we would map the pageno and the slot number?
That mapping is not needed at all?
Regards,
Amul
From | Date | Subject | |
---|---|---|---|
Next Message | Amul Sul | 2023-11-08 05:21:38 | Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock |
Previous Message | Andres Freund | 2023-11-08 04:24:45 | Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry |