Sv: Re: Query is over 2x slower with jit=on

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Sv: Re: Query is over 2x slower with jit=on
Date: 2018-04-18 16:26:03
Message-ID: VisenaEmail.27.2a4e4d7bcb66442e.162d991746c@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

På onsdag 18. april 2018 kl. 17:50:55, skrev Andres Freund <andres(at)anarazel(dot)de
On 2018-04-18 17:35:31 +0200, Andreas Joseph Krogh wrote:
> With jit=on:
> 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
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com> <>


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2018-04-18 16:27:41 Re: Query is over 2x slower with jit=on
Previous Message Yuriy Zhuravlev 2018-04-18 16:03:14 Re: Setting rpath on