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

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Sv: Re: Query is over 2x slower with jit=on
Date: 2018-08-22 16:39:18
Message-ID: VisenaEmail.27.cb06f4d2cef742ad.165627feef4@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

På onsdag 22. august 2018 kl. 18:12:41, skrev Andres Freund <andres(at)anarazel(dot)de
<mailto:andres(at)anarazel(dot)de>>:
Hi,

On 2018-04-18 18:37:30 -0400, Robert Haas wrote:
> On Wed, Apr 18, 2018 at 3:29 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > Not convinced that that is true - the issue is more likely that JIT work
in workers is counted as execute time... Gotta add that somehow, not sure what
the best way would be.
>
> Oh, that does seem like something that should be fixed.  If that's
> what is happening here, it's bound to confuse a lot of people.
> Probably you need to add some code to
> ExecParallelRetrieveInstrumentation.

I had lost track of this, and we unfortunately hadn't added an open item
back then.  I think we should add it now?

RMT (with me recused), do you think we should accept the new code fixing
this would entail? And thus that this should be an open item? It's
arguably a new feature, although I don't find that a terribly convincing
position.

Greetings,

Andres Freund
 
Just to be clear; The query really runs slower (wall-clock time), it's not
just the timing.
 
--
Andreas Joseph Krogh

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-08-22 16:39:38 Re: Stored procedures and out parameters
Previous Message Jonathan S. Katz 2018-08-22 16:36:34 Re: Query is over 2x slower with jit=on