From: Justin Pryzby <pryzby@telsasoft.com>
To: Andreas Joseph Krogh <andreas@visena.com>
Cc: Tobias Gierke <tobias.gierke@code-sourcery.de>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL mailing lists <pgsql-performance@postgresql.org>
Subject: Re: Sv: JIT in PostgreSQL 12 ?
Date: Fri, 31 May 2019 18:38:23 -0500
Message-ID: <20190531233822.GR27382@telsasoft.com> (raw)
In-Reply-To: <VisenaEmail.21.c9f137cb2e7b98d4.16b02c4aacc@tc7-visena>
References: <b1705e1a-90dc-f614-74cb-2e003a457758@code-sourcery.de>
<VisenaEmail.21.c9f137cb2e7b98d4.16b02c4aacc@tc7-visena>
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.gierke@code-sourcery.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, andreas@visena.com, tobias.gierke@code-sourcery.de, andres@anarazel.de
Subject: Re: Sv: JIT in PostgreSQL 12 ?
In-Reply-To: <20190531233822.GR27382@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox