Re: Why JIT speed improvement is so modest?

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: Why JIT speed improvement is so modest?
Дата
Msg-id CAHyXU0xdckw6JkV9B-YrOh33KGFLrQwD_FVSEXFvZ7st-M59ZA@mail.gmail.com
обсуждение исходный текст
Ответ на Why JIT speed improvement is so modest?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Ответы Re: Why JIT speed improvement is so modest?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Список pgsql-hackers
On Mon, Nov 25, 2019 at 9:09 AM Konstantin Knizhnik
<k.knizhnik@postgrespro.ru> wrote:
> JIT was not able to significantly (times) increase speed on Q1 query?
> Experiment with VOPS shows that used aggregation algorithm itself is not
> a bottleneck.
> Profile also give no answer for this question.
> Any ideas?

Well, in the VOPS variant around 2/3 of the time is spent in routines
that are obviously aggregation.  In the JIT version, it's around 20%.
So this suggests that the replacement execution engine is more
invasive.  I would also guess (!) that the VOPS engine optimizes fewer
classes of query plan.   ExecScan for example, looks to be completely
optimized out VOPS but is still utilized in the JIT engine.

I experimented with Vitessa a couple of years back and this was
consistent with my recollection.

merlin



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Konstantin Knizhnik
Дата:
Сообщение: Why JIT speed improvement is so modest?
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: [HACKERS] Block level parallel vacuum