Re: Query is over 2x slower with jit=on - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Query is over 2x slower with jit=on
Date
Msg-id CA+TgmoYQmR3Yr384jxZaw8r6KzKM38Z94v0egDbx5V-zEiWV4w@mail.gmail.com
Whole thread Raw
In response to Re: Query is over 2x slower with jit=on  (Andres Freund <andres@anarazel.de>)
Responses Re: Query is over 2x slower with jit=on
List pgsql-hackers
On Wed, Apr 18, 2018 at 11:50 AM, Andres Freund <andres@anarazel.de> wrote:
> JIT has cost, and sometimes it's not beneficial. Here our heuristics
> when to JIT appear to be a bit off. In the parallel world it's worse
> because the JITing is duplicated for parallel workers atm.

It seems like you're describing it as if the JIT just didn't produce
gains sufficient to make up for the cost of doing it, but that's not
really the issue here AFAICS.  Here the JIT actually made code that
run slower than the un-JIT-ted code.  That seems like a different sort
of problem.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: Proposal: Adding json logging
Next
From: Andres Freund
Date:
Subject: Re: Query is over 2x slower with jit=on