Re: JIT overhead slowdown

Hi Andres,

yes please it would be much apreciated. Would it not be possible to share the jitted program across the workers?

Cheers,
Luis

Dr. Luis M. Carril Rodríguez
Senior Software Engineer
luis(dot)carril(at)swarm64(dot)com<mailto:lisa(at)swarm64(dot)com>

Swarm64 AS
Parkveien 41 B | 0258 Oslo | Norway
Registered at Brønnøysundregistrene in Norway under Org.-Number 911 662 787
CEO/Geschäftsführer (Daglig Leder): Dr. Karsten Rönner; Chairman/Vorsitzender (Styrets Leder): Dr. Sverre Munck

Swarm64 AS Zweigstelle Hive
Ullsteinstr. 120 | 12109 Berlin | Germany

Registered at Amtsgericht Charlottenburg - HRB 154382 B

[cid:01158560-9a6f-4435-8170-02d99a0c9cd0]
________________________________
From: Andres Freund <andres(at)anarazel(dot)de>
Sent: Friday, January 18, 2019 5:42:54 PM
To: Luis Carril
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: JIT overhead slowdown

Hi,

On 2019-01-18 14:12:23 +0000, Luis Carril wrote:
> Is this behavior expected? Is the cost function for jitting missing some circumstances?

The costing doesn't take the effect of overhead of repeated JITing in
each worker into account. I could give you a test patch that does, if
you want to play around with it?

Greetings,

Andres Freund