pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedSv: JIT in PostgreSQL 12 ?
4+ messages / 3 participants
[nested] [flat]
* Sv: JIT in PostgreSQL 12 ?
@ 2019-05-29 08:48 Andreas Joseph Krogh <andreas@visena.com>
0 siblings, 2 replies; 4+ messages in thread
From: Andreas Joseph Krogh @ 2019-05-29 08:48 UTC (permalink / raw)
To: Tobias Gierke <tobias.gierke@code-sourcery.de>; +Cc: pgsql-performance
På onsdag 29. mai 2019 kl. 10:02:50, skrev Tobias Gierke <
tobias.gierke@code-sourcery.de <mailto: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. -- Andreas
Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963 andreas@visena.com
<mailto:andreas@visena.com> www.visena.com <https://www.visena.com;
<https://www.visena.com;
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Sv: JIT in PostgreSQL 12 ?
@ 2019-05-29 09:13 Tobias Gierke <tobias.gierke@code-sourcery.de>
parent: Andreas Joseph Krogh <andreas@visena.com>
1 sibling, 1 reply; 4+ messages in thread
From: Tobias Gierke @ 2019-05-29 09:13 UTC (permalink / raw)
To: pgsql-performance@lists.postgresql.org
Hi,
> På onsdag 29. mai 2019 kl. 10:02:50, skrev Tobias Gierke
> <tobias.gierke@code-sourcery.de <mailto: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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Sv: JIT in PostgreSQL 12 ?
@ 2019-05-29 09:16 Andreas Joseph Krogh <andreas@visena.com>
parent: Tobias Gierke <tobias.gierke@code-sourcery.de>
0 siblings, 0 replies; 4+ messages in thread
From: Andreas Joseph Krogh @ 2019-05-29 09:16 UTC (permalink / raw)
To: Tobias Gierke <tobias.gierke@code-sourcery.de>; +Cc: pgsql-performance@lists.postgresql.org
På onsdag 29. mai 2019 kl. 11:13:10, skrev Tobias Gierke <
tobias.gierke@code-sourcery.de <mailto:tobias.gierke@code-sourcery.de>>: Hi, På
onsdag 29. mai 2019 kl. 10:02:50, skrev Tobias Gierke <
tobias.gierke@code-sourcery.de <mailto: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.
That's what we'll do, unfortunately:-( -- Andreas Joseph Krogh CTO / Partner -
Visena AS Mobile: +47 909 56 963 andreas@visena.com <mailto:andreas@visena.com>
www.visena.com <https://www.visena.com; <https://www.visena.com;
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Sv: JIT in PostgreSQL 12 ?
@ 2019-05-31 23:38 Justin Pryzby <pryzby@telsasoft.com>
parent: Andreas Joseph Krogh <andreas@visena.com>
1 sibling, 0 replies; 4+ messages in thread
From: Justin Pryzby @ 2019-05-31 23:38 UTC (permalink / raw)
To: Andreas Joseph Krogh <andreas@visena.com>; +Cc: Tobias Gierke <tobias.gierke@code-sourcery.de>; Andres Freund <andres@anarazel.de>; 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.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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2019-05-31 23:38 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-05-29 08:48 Sv: JIT in PostgreSQL 12 ? Andreas Joseph Krogh <andreas@visena.com>
2019-05-29 09:13 ` Tobias Gierke <tobias.gierke@code-sourcery.de>
2019-05-29 09:16 ` Andreas Joseph Krogh <andreas@visena.com>
2019-05-31 23:38 ` Justin Pryzby <pryzby@telsasoft.com>
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