From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | Joel Jacobson <joel(at)compiler(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Is *fast* 32-bit support still important? |
Date: | 2024-07-30 07:25:06 |
Message-ID: | 200fd50d-879c-4e9d-80c8-8e9477611003@iki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 29/07/2024 23:40, Joel Jacobson wrote:
> To me, it's non-obvious whether introducing `#if SIZEOF_DATUM < 8` with
> separate 32-bit and 64-bit code paths is worthwhile to maintain performance
> for both.
>
> Knowing more about $subject can hopefully help us reason about how much
> additional code complication is justifiable for *fast* 32-bit support.
IMO I don't think it's worth adding extra code for fast 32-bit support
anymore. However, I'd still be wary of *regressing* performance on
32-bit systems.
So if you're adding a new fast path to a function, it's OK to make it
64-bit only, and fall back to the old slower code on 32-bit systems. But
-1 on *removing* existing 32-bit fast path code, or rewriting things in
a way that makes an existing function significantly slower than before
on 32-bit systems.
This isn't black or white though. It depends on how big a gain or
regression we're talking about, and how complex the extra code would be.
--
Heikki Linnakangas
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2024-07-30 07:36:00 | Re: A problem about partitionwise join |
Previous Message | Anthonin Bonnefoy | 2024-07-30 07:21:25 | Re: Use pgBufferUsage for block reporting in analyze |