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

From Andres Freund
Subject Re: Query is over 2x slower with jit=on
Date
Msg-id 20180925201723.5w6ouwlpjf75dzgh@alap3.anarazel.de
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  (Lukas Fittl <lukas@fittl.com>)
List pgsql-hackers
Hi,

On 2018-09-25 12:50:34 -0700, Andres Freund wrote:
> On 2018-09-25 01:47:49 -0700, Andres Freund wrote:
> > Planning Time: 0.152 ms
> > JIT:
> >   Functions: 4
> >   Options: Inlining true, Optimization true, Expressions true, Deforming true
> >   Timing: Generation 0.955 ms, Inlining 157.422 ms, Optimization 11.751 ms, Emission 11.454 ms, Total 181.582 ms
> > Execution Time: 184.197 ms
> 
> With parallelism on, this is the aggregated cost of doing JIT
> compilation. I wonder if, in VERBOSE mode, we should separately display
> the cost of JIT for the leader.  Comments?

I've pushed the change without that bit - it's just a few additional
lines if we want to change that.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Query is over 2x slower with jit=on
Next
From: Chapman Flack
Date:
Subject: clarify documentation of BGW_NEVER_RESTART ?