From: Mladen Gogala <gogala.mladen@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Catching up with performance & PostgreSQL 15
Date: Tue, 29 Nov 2022 19:44:23 -0500
Message-ID: <bcd915ceb9bb65f1a4e00b673371071c63146a4f.camel@gmail.com> (raw)
In-Reply-To: <20221129180914.pdrqrbqtls3g6yoq@alvherre.pgsql>
References: <20221129180914.pdrqrbqtls3g6yoq@alvherre.pgsql>
On Tue, 2022-11-29 at 19:09 +0100, Alvaro Herrera wrote:
> On 2022-Nov-29, Mladen Gogala wrote:
>
> > Hmmm, I think I will run pgbench with and without JIT on and see
> > the
> > difference.
>
> I doubt you'll notice anything, because the pgbench queries will be
> far
> below the JIT cost, so nothing will get JIT compiled at all. Or are
> you
> planning on using a custom set of queries?
>
Nope. I am planning to set jit_above_cost parameter to 5. That should
take care of the pgbench problem. Other than that, you're right: JIT
should not be used for OLTP. However, pure OLTP or DW databases are a
rarity these days. Reporting is a crucial function and almost every
OLTP database that I've seen also has reporting function, which means
that there are complex queries to be executed.
--
Mladen Gogala
Database Consultant
https://dbwhisperer.wordpress.com
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: gogala.mladen@gmail.com, alvherre@alvh.no-ip.org, pgsql-performance@lists.postgresql.org
Subject: Re: Catching up with performance & PostgreSQL 15
In-Reply-To: <bcd915ceb9bb65f1a4e00b673371071c63146a4f.camel@gmail.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