Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p01Qo-0002tp-24 for pgsql-performance@arkaria.postgresql.org; Tue, 29 Nov 2022 14:17:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p01Qm-0000rp-Tc for pgsql-performance@arkaria.postgresql.org; Tue, 29 Nov 2022 14:17:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p01Qm-0000rf-Jg for pgsql-performance@lists.postgresql.org; Tue, 29 Nov 2022 14:17:52 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p01Qk-0002Qr-B4 for pgsql-performance@lists.postgresql.org; Tue, 29 Nov 2022 14:17:52 +0000 Received: by mail-qt1-x835.google.com with SMTP id c15so8943365qtw.8 for ; Tue, 29 Nov 2022 06:17:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=IOT57QfUD6DK+2wjriypILym65OzwziRvu7/6t7u4Bo=; b=DcCt5qzpU52t977sMY7AJPZ6V3hTdz2sLFEo7ePZPuzBiD1VSm2nxSomJMvAIGJFcX axbKOdpnQ5IBdNavHvM0eojhmWWx65hSXLL/uXtkI0vqg2MnHOV/QbjprsfEPw2SPvgu Ozu33ud4uoXm/q76oQetZUCqm/0KgsYb4uNExcTzCV6LEACvX/mn6FNfBSlopy+MJUHF x2CbnOGBrZiGtCMinLxfhspy5ohj8UdrmqLTpgAqK85KfDX+nbCr55k9JO8ddVM4PaLz 6VJR0l4t3QkKBtnbscJOE27GFoda8YG5tmIYXjRYXdta/TUKMvKY9vqGChsj+xqQtT4g KlPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=IOT57QfUD6DK+2wjriypILym65OzwziRvu7/6t7u4Bo=; b=ElX3QMqTFyqGy5nIQSKl7ZeoMtY8EJkPaPHQ6shsER2fa0m7muyPYpW3fibyVNl/v3 rIWKCsqBTDfz/Cb2eu2pCvqeblTA5exj8yrOTuPYkKOaZpqSKwI1PRCHsZsoqPNpeWgw m2Svmk+FUj6f8hNEZrcsl5DUt4iXLdaT1gpSu8pIjSAR7nY9pbNf8eDLryKlcVHE87t/ byykYiF/K2gXosHeqd26Bq9DaAMRkVl1dUGvjrRWjK/rTJBUdSO6lMLCLEeILhwlWyFj H+Js9Y+BahN345wh9w5pV0wjXMTzhRwGpcs8OlCXkNkR3bVFOAKJP2YgVD50jrGa4eke W06Q== X-Gm-Message-State: ANoB5plGak+35w99cD7D5w598tLTK92CxnIMp4AdUFFOfj0DaNM5gTno cCfAHJ0AKuK99aln7tonSjbm7jPR/jN2Lw== X-Google-Smtp-Source: AA0mqf6mNPeVfJs4Ya+Xu5CYtfjwhEiPGCBhcgV9Am6mVqTElJe2idW+3G8RSZUB8Mkgqs6NZ45YnQ== X-Received: by 2002:ac8:4403:0:b0:3a5:3cc0:8139 with SMTP id j3-20020ac84403000000b003a53cc08139mr33696126qtn.533.1669731468665; Tue, 29 Nov 2022 06:17:48 -0800 (PST) Received: from [192.168.2.100] (pool-72-79-30-4.nwrknj.east.verizon.net. [72.79.30.4]) by smtp.gmail.com with ESMTPSA id dt31-20020a05620a479f00b006fbf88667bcsm10588524qkb.77.2022.11.29.06.17.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Nov 2022 06:17:48 -0800 (PST) Content-Type: multipart/alternative; boundary="------------iSZV2B40rWpK5mL6Os8qNSG0" Message-ID: <401ac59b-067f-28f2-547d-417ee5c49c39@gmail.com> Date: Tue, 29 Nov 2022 09:17:48 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: Catching up with performance & PostgreSQL 15 Content-Language: en-US To: Alvaro Herrera Cc: pgsql-performance@lists.postgresql.org References: <20221129083615.fseqfvd5svtjbrb6@alvherre.pgsql> From: Mladen Gogala In-Reply-To: <20221129083615.fseqfvd5svtjbrb6@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------iSZV2B40rWpK5mL6Os8qNSG0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 11/29/22 03:36, Alvaro Herrera wrote: > On 2022-Nov-28, Mladen Gogala wrote: > >> As for JIT, I've recently asked that question myself. I was told that >> PostgreSQL with LLVM enabled performs approximately 25% better than without >> it. > Hmm, actually, normally you're better off turning JIT off, because it's > very common to diagnose cases of queries that become much, much slower > because of it. Some queries do become faster, but it's not a wide > margin, and it's not a lot. There are rare cases where JIT is > beneficial, but those tend to be queries that take upwards of several > seconds already. > > IMO it was a mistake to turn JIT on in the default config, so that's one > thing you'll likely want to change. > Hmmm, I think I will run pgbench with and without JIT on and see the difference. -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com --------------iSZV2B40rWpK5mL6Os8qNSG0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
On 11/29/22 03:36, Alvaro Herrera wrote:
On 2022-Nov-28, Mladen Gogala wrote:

As for JIT, I've recently asked that question myself. I was told that
PostgreSQL with LLVM enabled performs approximately 25% better than without
it.
Hmm, actually, normally you're better off turning JIT off, because it's
very common to diagnose cases of queries that become much, much slower
because of it.  Some queries do become faster, but it's not a wide
margin, and it's not a lot.  There are rare cases where JIT is
beneficial, but those tend to be queries that take upwards of several
seconds already.

IMO it was a mistake to turn JIT on in the default config, so that's one
thing you'll likely want to change.

Hmmm, I think I will run pgbench with and without JIT on and see the difference.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
--------------iSZV2B40rWpK5mL6Os8qNSG0--