From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
Cc: | Tobias Gierke <tobias(dot)gierke(at)code-sourcery(dot)de>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Sv: JIT in PostgreSQL 12 ? |
Date: | 2019-05-31 23:38:23 |
Message-ID: | 20190531233822.GR27382@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, May 29, 2019 at 10:48:19AM +0200, Andreas Joseph Krogh wrote:
> På onsdag 29. mai 2019 kl. 10:02:50, skrev Tobias Gierke <tobias(dot)gierke(at)code-sourcery(dot)de>
> Hi,
>
> Browsing the PostgreSQL 12 release notes I noticed that JIT is now
> enabled by default. Having not followed PostgreSQL development closely -
> does this mean that compilation results are now getting cached and
> compilation is no longer executed separately for each worker thread in a
> parallel query ?
Thanks for starting the conversation.
> I don't know, but just want to chime in with my experience
> with PG-12 and JIT: Execution-time is still way worse then JIT=off for your
> queries so we'll turn JIT=off until we can mesure performance-gain.
That's also been my consistent experience and conclusion.
I gather the presumption has been that JIT will be enabled by default..
..but perhaps this is a "Decision to Recheck Mid-Beta" (?)
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Haroldo Kerry | 2019-06-01 13:17:13 | Re: Shortest offline window on database migration |
Previous Message | Fabio Pardi | 2019-05-31 11:54:26 | Re: improve wals replay on secondary |