Re: Query JITing with LLVM ORC - Mailing list pgsql-hackers

From João Paulo Labegalini de Carvalho
Subject Re: Query JITing with LLVM ORC
Date
Msg-id CAGjvy2_nNALRnYJiko99DS1eXMPsdfzPXXaToWQT03idrkNLcg@mail.gmail.com
Whole thread Raw
In response to Re: Query JITing with LLVM ORC  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Tom & Thomas:

Thank you so much, those a very useful comments.

I noticed that I didn't make my intentions very clear. My teams goal is to evaluate if there are any gains in JITing PostgreSQL itself, or at least parts of it, and not the expressions or parts of a query.

The rationale to use PostgreSQL is because DBs are long running applications and the cost of JITing can be amortized.

We have a prototype LLVM IR pass that outlines functions in a program to JIT and a ORC-based runtime to re-compile functions. Our goal is to see improvements due to target/sub-target specialization.

The reason I was looking at benchmarks is to have a workload to profile PostgreSQL and find its bottlenecks. The hot functions would then be outlined for JITing.



On Wed., Sep. 21, 2022, 4:54 p.m. Thomas Munro, <thomas.munro@gmail.com> wrote:
On Thu, Sep 22, 2022 at 10:04 AM João Paulo Labegalini de Carvalho
<jaopaulolc@gmail.com> wrote:
>building with and w/o passing --with-llvm

BTW you can also just turn it off with runtime settings, no need to rebuild.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_basebackup's --gzip switch misbehaves
Next
From: Fujii Masao
Date:
Subject: Re: Fix snapshot name for SET TRANSACTION documentation