Re: New LLVM JIT Features

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Praveen Velliengiri <praveenvelliengiri(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: New LLVM JIT Features
Date: 2019-04-02 20:51:31
Message-ID: CA+hUKGJqeO10WM1bjRxDV7mEEtORMLG0ARqde88Fqd-jN_--Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 3, 2019 at 8:39 AM Praveen Velliengiri
<praveenvelliengiri(at)gmail(dot)com> wrote:
> On Apr 2, 2019 12:51 AM, "preejackie" <praveenvelliengiri(at)gmail(dot)com> wrote:
>> I'm Praveen Velliengiri, student from India. I'm working on developing a Speculative compilation support in LLVM ORC JIT Infrastructure.
>>
>> As LLVM ORC supports compiling in multiple backend threads, it would be effective if we compile the functions speculatively before they are called by the executing function. So when we request JIT to compile a function, JIT will immediately returns the function address for raw executable bits. This will greatly reduce the JIT latencies in modern multi-core machines. And also I'm working on designing a ORC in-place dynamic profiling support, by this JIT will automatically able to identify the hot functions, and compile it in higher optimization level to achieve good performance.
>>
>> I'm proposing this project for GSoC 2019. It would be helpful to know how this new features are effective to pgsql engine, so that I include your comments in "View from Clients" proposal section.

Hi Praveen,

FYI the final "commitfest" for PostgreSQL 12 is wrapping up right now
and the code freeze begins in a few days, so I wouldn't expect an
immediate reply.

--
Thomas Munro
https://enterprisedb.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andres Freund 2019-04-02 21:50:21 Re: New LLVM JIT Features
Previous Message Adrian Klaver 2019-04-02 20:43:13 Re: max_prepared_foreign_transactions is unrecognized