Sv: Re: Query is over 2x slower with jit=on - Mailing list pgsql-hackers

From Andreas Joseph Krogh
Subject Sv: Re: Query is over 2x slower with jit=on
Date
Msg-id VisenaEmail.27.cb06f4d2cef742ad.165627feef4@tc7-visena
Whole thread Raw
In response to Re: Query is over 2x slower with jit=on  (Andres Freund <andres@anarazel.de>)
Responses Re: Query is over 2x slower with jit=on
List pgsql-hackers
På onsdag 22. august 2018 kl. 18:12:41, skrev Andres Freund <andres@anarazel.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@anarazel.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

pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: Query is over 2x slower with jit=on
Next
From: Peter Eisentraut
Date:
Subject: Re: Stored procedures and out parameters