From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | Tobias Gierke <tobias(dot)gierke(at)code-sourcery(dot)de> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Sv: JIT in PostgreSQL 12 ? |
Date: | 2019-05-29 09:16:06 |
Message-ID: | VisenaEmail.26.b2cf86e2c6fa0fb1.16b02df9deb@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
På onsdag 29. mai 2019 kl. 11:13:10, skrev Tobias Gierke <
tobias(dot)gierke(at)code-sourcery(dot)de <mailto:tobias(dot)gierke(at)code-sourcery(dot)de>>: Hi, På
onsdag 29. mai 2019 kl. 10:02:50, skrev Tobias Gierke <
tobias(dot)gierke(at)code-sourcery(dot)de <mailto: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 ? 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(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com> <https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2019-05-29 09:37:04 | Re: JIT in PostgreSQL 12 ? |
Previous Message | Tobias Gierke | 2019-05-29 09:13:10 | Re: Sv: JIT in PostgreSQL 12 ? |