From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Query performance in 9.6.24 vs 14.10 |
Date: | 2024-01-29 16:52:54 |
Message-ID: | CANzqJaCgUXCiaYo=47dc=xPHAXC-zj=YivYuZ0_HNAnJ55muRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
According to my tests, sometimes JIT is a little faster, and sometimes it's
a little slower. Mostly within the realm of statistical noise (especially
with each query having a sample size of only 13, on a VM that lives on a
probably-busy host).
On Mon, Jan 29, 2024 at 9:18 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> Yes, jit=on.
>
> I'll test them with jit=off, to see the difference. (The application is
> 3rd party, so will change it at the system level.)
>
> On Mon, Jan 29, 2024 at 7:09 AM Bob Jolliffe <bobjolliffe(at)gmail(dot)com>
> wrote:
>
>> Out of curiosity, is the pg14 running with the default jit=on setting?
>>
>> This is obviously entirely due to the nature of the particular queries
>> themselves, but we found that for our workloads that pg versions
>> greater than 11 were exacting a huge cost due to the jit compiler. Once we
>> explicitly turned jit=off we started to see improvements.
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shaheed Haque | 2024-01-29 17:28:32 | Re: Scriptable way to validate a pg_dump restore ? |
Previous Message | Adrian Klaver | 2024-01-29 16:52:16 | Re: Scriptable way to validate a pg_dump restore ? |