Re: Difference in execution plans pg12 vs pg14
| От | Дмитрий Иванов |
|---|---|
| Тема | Re: Difference in execution plans pg12 vs pg14 |
| Дата | |
| Msg-id | CAPL5KHq8zfWPzueCemXw4c+U568PoDfqo3wBDNm3KAyvybdaMQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Difference in execution plans pg12 vs pg14 (Imre Samu <pella.samu@gmail.com>) |
| Список | pgsql-general |
Ok, I will check.
Now I have even more questions. This behavior appeared, it was not there in the first place. jit-compilation down my long aggregation queries by about half on average. How do I adjust this correctly?
#jit_provider = 'llvmjit' # JIT library to use
#jit_above_cost = 100000 # perform JIT compilation if available
# and query more expensive than this;
# -1 disables
#jit_inline_above_cost = 500000 # inline small functions if query is
# more expensive than this; -1 disables
#jit_optimize_above_cost = 500000 # use expensive JIT optimizations if
# query is more expensive than this;
# -1 disables
jit = off # allow JIT compilation
# and query more expensive than this;
# -1 disables
#jit_inline_above_cost = 500000 # inline small functions if query is
# more expensive than this; -1 disables
#jit_optimize_above_cost = 500000 # use expensive JIT optimizations if
# query is more expensive than this;
# -1 disables
jit = off # allow JIT compilation
--
Regards, Dmitry!сб, 11 дек. 2021 г. в 09:12, Imre Samu <pella.samu@gmail.com>:
Hi Dmitry,pg12:> Execution Time: 44.123 mspg14:> JIT:
> Functions: 167
> Options: Inlining true, Optimization true, Expressions true, Deforming true
> Timing: Generation 9.468 ms, Inlining 55.237 ms, Optimization 507.548 ms, Emission 347.932 ms, Total 920.185 ms
> Execution Time: 963.258 msplease check the JIT settings ;and test with: jit = off;regards,ImreДмитрий Иванов <firstdismay@gmail.com> ezt írta (időpont: 2021. dec. 11., Szo, 2:01):Afternoon. I was able to make the necessary changes to my base needed to migrate win_pg12 to debian pg14.
But there is a new problem, which was not there at the initial stage so I checked:
win_pg12:
-> Index Scan using index_class_tree_full on class c (cost=0.28..2.50 rows=1 width=235) (actual time=0.030..0.032 rows=1 loops=1)
Index Cond: (id = 650)
debian_pg14:
-> Index Scan using index_class_tree_full on class c (cost=0.28..2.50 rows=1 width=235) (actual time=842.795..842.796 rows=1 loops=1)
Index Cond: (id = 650)
I'm wondering where to dig next...--Best regards, Dmitry!
Вложения
В списке pgsql-general по дате отправления: