pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mladen Gogala <gogala.mladen@gmail.com>
To: Kenny Bachman <kenny.bachman17@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Postgresql 14 performance
Date: Sun, 21 Aug 2022 18:49:15 -0400
Message-ID: <060a5606-86f8-4d36-999e-89e78a808096@gmail.com> (raw)
In-Reply-To: <CAC0w7L+HMwF9f5uuhHnwkaTqPemdKWscmRhYTP2Uq7-i3XaEAw@mail.gmail.com>
References: <CAC0w7LL+uFgPvctiHMxrVZV-DnNVg2K_wFaeZwM96XQFkjk1uA@mail.gmail.com>
	<62c9a8d8-8c0f-3c11-5cca-e05e126c25d8@gmail.com>
	<CAC0w7L+ezaB8tw-kh6rZC0RhG8ZwhLG_EkUErGEiUQ=f8uAC6g@mail.gmail.com>
	<1821f1b5-aabc-6cc6-1d5b-26381c6270d9@gmail.com>
	<CAC0w7L+HMwF9f5uuhHnwkaTqPemdKWscmRhYTP2Uq7-i3XaEAw@mail.gmail.com>

On 8/21/22 16:13, Kenny Bachman wrote:
> Hi again,
>
> JIT is already enabled. And here is the perf top output:
>
Kenny, JIT is not mentioned in any of your plans. Look how it looks, 
with JIT enabled:

QUERY PLAN
-------------------------------------------------------------------------------------------------------
  Aggregate  (cost=1682569.70..1682569.71 rows=1 width=8)
    ->  Nested Loop  (cost=0.00..1419035.94 rows=105413504 width=0)
          ->  Nested Loop  (cost=0.00..101365.96 rows=7529536 width=0)
                ->  Nested Loop  (cost=0.00..7245.59 rows=537824 width=0)
                      ->  Nested Loop  (cost=0.00..521.62 rows=38416 
width=0)
                            ->  Nested Loop  (cost=0.00..40.24 rows=2744 
width=0)
                                  ->  Nested Loop (cost=0.00..4.77 
rows=196 width=0)
                                        ->  Seq Scan on emp e1  
(cost=0.00..1.14 rows=14 width=0)
                                        ->  Materialize (cost=0.00..1.21 
rows=14 width=0)
                                              ->  Seq Scan on emp e2  
(cost=0.00..1.14 rows=14 width=0)
                                  ->  Materialize (cost=0.00..1.21 
rows=14 width=0)
                                        ->  Seq Scan on emp e3  
(cost=0.00..1.14 rows=14 width=0)
                            ->  Materialize  (cost=0.00..1.21 rows=14 
width=0)
                                  ->  Seq Scan on emp e4 
(cost=0.00..1.14 rows=14 width=0)
                      ->  Materialize  (cost=0.00..1.21 rows=14 width=0)
                            ->  Seq Scan on emp e5 (cost=0.00..1.14 
rows=14 width=0)
                ->  Materialize  (cost=0.00..1.21 rows=14 width=0)
                      ->  Seq Scan on emp e6  (cost=0.00..1.14 rows=14 
width=0)
          ->  Materialize  (cost=0.00..1.21 rows=14 width=0)
                ->  Seq Scan on emp e7  (cost=0.00..1.14 rows=14 width=0)
* JIT:**
**   Functions: 14**
**   Options: Inlining true, Optimization true, Expressions true, 
Deforming true**
**(23 rows)*

Look at the end. There is no such section in any of your plans.

Regards

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

view thread (20+ messages)  latest in thread

Message-ID: <060a5606-86f8-4d36-999e-89e78a808096@gmail.com>
Permalink:  ../060a5606-86f8-4d36-999e-89e78a808096@gmail.com/
Also on:    postgresql.org/message-id/060a5606-86f8-4d36-999e-89e78a808096@gmail.com

 · 

reply

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-admin@postgresql.org
  Cc: gogala.mladen@gmail.com, kenny.bachman17@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Postgresql 14 performance
  In-Reply-To: <060a5606-86f8-4d36-999e-89e78a808096@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