Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hVueD-0007rm-I0 for pgsql-performance@arkaria.postgresql.org; Wed, 29 May 2019 09:13:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hVue9-0003jz-Ks for pgsql-performance@arkaria.postgresql.org; Wed, 29 May 2019 09:13:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hVue9-0003js-8O for pgsql-performance@lists.postgresql.org; Wed, 29 May 2019 09:13:21 +0000 Received: from mail2.code-sourcery.de ([138.201.66.53]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hVue2-0003RO-3a for pgsql-performance@lists.postgresql.org; Wed, 29 May 2019 09:13:20 +0000 Received: from lxtobi.voipfuture.com (unknown [213.238.34.194]) by mail2.code-sourcery.de (Postfix) with ESMTPSA id 2D1AC1FE79 for ; Wed, 29 May 2019 11:13:11 +0200 (CEST) Subject: Re: Sv: JIT in PostgreSQL 12 ? To: pgsql-performance@lists.postgresql.org References: From: Tobias Gierke Message-ID: <463322dc-8b64-3595-7f48-3c513d81bd0a@code-sourcery.de> Date: Wed, 29 May 2019 11:13:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------0EBE9EDF998A134287B44833" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------0EBE9EDF998A134287B44833 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, > På onsdag 29. mai 2019 kl. 10:02:50, skrev Tobias Gierke > >: > > 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 ? > > 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. Hm, that's a bummer. So I guess we'll also have to make sure JIT is turned off when upgrading. Thanks, Tobias --------------0EBE9EDF998A134287B44833 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

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 ?

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.

Hm, that's a bummer. So I guess we'll also have to make sure JIT is turned off when upgrading.

Thanks,
Tobias

--------------0EBE9EDF998A134287B44833--