Re: JIT compilation per plan node - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: JIT compilation per plan node
Date
Msg-id bd1f1eeb-e0e5-4258-b7e2-e66b4beb37a8@enterprisedb.com
Whole thread Raw
In response to Re: JIT compilation per plan node  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: JIT compilation per plan node
List pgsql-hackers
On 2/20/24 06:38, David Rowley wrote:
> On Tue, 20 Feb 2024 at 18:31, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> FWIW, I seriously doubt that an extra walk of the plan tree is even
>> measurable compared to the number of cycles JIT compilation will
>> expend if it's called.  So I don't buy your argument here.
>> We would be better off to do this in a way that's clean and doesn't
>> add overhead for non-JIT-enabled builds.
> 
> The extra walk of the tree would need to be done for every plan, not
> just the ones where we do JIT. I'd rather find a way to not add this
> extra plan tree walk, especially since the vast majority of cases on
> an average instance won't be doing any JIT.
> 

I believe Tom was talking about non-JIT-enabled-builds, i.e. builds that
either don't support JIT at all, or where jit=off. Those would certainly
not need the extra walk.

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Add bump memory context type and use it for tuplesorts
Next
From: Quan Zongliang
Date:
Subject: Change the bool member of the Query structure to bits