From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | Tobias Gierke <tobias(dot)gierke(at)code-sourcery(dot)de> |
Cc: | PostgreSQL mailing lists <pgsql-performance(at)postgresql(dot)org> |
Subject: | Sv: JIT in PostgreSQL 12 ? |
Date: | 2019-05-29 08:48:19 |
Message-ID: | VisenaEmail.21.c9f137cb2e7b98d4.16b02c4aacc@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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. -- 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 | Tobias Gierke | 2019-05-29 09:13:10 | Re: Sv: JIT in PostgreSQL 12 ? |
Previous Message | Mariel Cherkassky | 2019-05-29 08:39:33 | Re: improve wals replay on secondary |