Re: Query JITing with LLVM ORC

From: João Paulo Labegalini de Carvalho <jaopaulolc(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Query JITing with LLVM ORC
Date: 2022-09-22 03:53:11
Message-ID: CAGjvy2_nNALRnYJiko99DS1eXMPsdfzPXXaToWQT03idrkNLcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)munro(at)gmail(dot)com>
wrote:

> On Thu, Sep 22, 2022 at 10:04 AM João Paulo Labegalini de Carvalho
> <jaopaulolc(at)gmail(dot)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.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2022-09-22 04:00:36 Re: Fix snapshot name for SET TRANSACTION documentation
Previous Message Tom Lane 2022-09-22 03:43:56 Re: pg_basebackup's --gzip switch misbehaves