Re: Stampede of the JIT compilers - Mailing list pgsql-hackers

From James Coleman
Subject Re: Stampede of the JIT compilers
Date
Msg-id CAAaqYe9VSosjFXbW6qXnC9bZgCXsyM7o6dF6z02E41sqvg8wxg@mail.gmail.com
Whole thread Raw
In response to Re: Stampede of the JIT compilers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Jun 24, 2023 at 1:54 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> James Coleman <jtc331@gmail.com> writes:
> > In that context capping the number of backends compiling, particularly
> > where plans (and JIT?) might be cached, could well save us (depending
> > on workload).
>
> TBH I do not find this proposal attractive in the least.  We have
> a problem here even when you consider a single backend.  If we fixed
> that, so that we don't invoke JIT unless it really helps, then it's
> not going to help less just because you have a lot of backends.
> Plus, the overhead of managing a system-wide limit is daunting.
>
>                         regards, tom lane

I'm happy to withdraw that particular idea. My mental model was along
the lines "this is a startup cost, and then we'll have it cached, so
the higher than expected cost won't matter as much when the system
settles down", and in that scenario limiting the size of the herd can
make sense.

But that's not the broader problem, so...

Regards,
James Coleman



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Add support for AT LOCAL
Next
From: James Coleman
Date:
Subject: Re: Stampede of the JIT compilers