Re: Query is over 2x slower with jit=on
От | Andres Freund |
---|---|
Тема | Re: Query is over 2x slower with jit=on |
Дата | |
Msg-id | 20180919224047.mcdjwis56ywqzhzs@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Query is over 2x slower with jit=on (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Query is over 2x slower with jit=on
|
Список | pgsql-hackers |
Hi, On 2018-09-17 17:50:15 -0400, Tom Lane wrote: > Amit Khandekar <amitdkhan.pg@gmail.com> writes: > > On 11 September 2018 at 14:50, Amit Khandekar <amitdkhan.pg@gmail.com> wrote: > >> On 10 September 2018 at 21:39, Andres Freund <andres@anarazel.de> wrote: > >>> On 2018-09-10 15:42:55 +0530, Amit Khandekar wrote: > >>>> I think we better show per-worker jit info also. > > Just to throw a contrarian opinion into this: I find the current EXPLAIN > output for JIT to be insanely verbose already. Hm, it'd have been nice to get that feedback a little bit earlier, I did inquire... Currently: JIT: Functions: 2 Generation Time: 0.680 ms Inlining: true Inlining Time: 7.591 ms Optimization: true Optimization Time: 20.522 ms Emission Time: 14.607 ms How about making that: JIT: Functions: 2 Options: Inlining, Optimization Times (Total, Generation, Inlining, Optimization, Emission): 43.4 ms, 0.680 ms, 7.591 ms, 20.522 ms, 14.607 ms or something similar? Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: