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

From Andreas Joseph Krogh
Subject Sv: Re: Query is over 2x slower with jit=on
Date
Msg-id VisenaEmail.27.2a4e4d7bcb66442e.162d991746c@tc7-visena
Whole thread Raw
In response to Re: Query is over 2x slower with jit=on  (Andres Freund <andres@anarazel.de>)
Responses Sv: Sv: Re: Query is over 2x slower with jit=on  (Andreas Joseph Krogh <andreas@visena.com>)
List pgsql-hackers
På onsdag 18. april 2018 kl. 17:50:55, skrev Andres Freund <andres@anarazel.de>:
On 2018-04-18 17:35:31 +0200, Andreas Joseph Krogh wrote:
> With jit=on:
> https://explain.depesz.com/s/vYB
> Planning Time: 0.336 ms
>  JIT:
>   Functions: 716
>   Generation Time: 78.404 ms
>   Inlining: false
>   Inlining Time: 0.000 ms
>   Optimization: false
>   Optimization Time: 43.916 ms
>   Emission Time: 600.031 ms

Any chance this is a debug LLVM build?


> What's the deal with jit making it slower?

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.
 
PostgreSQL is built with "--enable-debug --with-llvm". LLVM is the one which comes with Ubuntu-17.10.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
 
Attachment

pgsql-hackers by date:

Previous
From: Yuriy Zhuravlev
Date:
Subject: Re: Setting rpath on llvmjit.so?
Next
From: Simon Riggs
Date:
Subject: Re: Query is over 2x slower with jit=on