Re: Query is over 2x slower with jit=on

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Query is over 2x slower with jit=on
Дата
Msg-id 20180418155055.gawfkerzvy5rxpxe@alap3.anarazel.de
обсуждение исходный текст
Ответ на Query is over 2x slower with jit=on  (Andreas Joseph Krogh <andreas@visena.com>)
Ответы Sv: Re: Query is over 2x slower with jit=on  (Andreas Joseph Krogh <andreas@visena.com>)
Re: Query is over 2x slower with jit=on  (Simon Riggs <simon@2ndquadrant.com>)
Re: Query is over 2x slower with jit=on  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 2018-04-18 17:35:31 +0200, Andreas Joseph Krogh wrote:
> With jit=on:
> https://explain.depesz.com/s/vYB
> Planning Time: 0.336 ms 
>  JIT:
>   Functions: 716
>   Generation Time: 78.404 ms
>   Inlining: false
>   Inlining Time: 0.000 ms
>   Optimization: false
>   Optimization Time: 43.916 ms
>   Emission Time: 600.031 ms

Any chance this is a debug LLVM build?


> What's the deal with jit making it slower?

JIT has cost, and sometimes it's not beneficial. Here our heuristics
when to JIT appear to be a bit off. In the parallel world it's worse
because the JITing is duplicated for parallel workers atm.

Greetings,

Andres Freund


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

Предыдущее
От: Julian Markwort
Дата:
Сообщение: Re: [FEATURE PATCH] pg_stat_statements with plans (v02)
Следующее
От: Yuriy Zhuravlev
Дата:
Сообщение: Re: Setting rpath on llvmjit.so?