JIT overhead slowdown - Mailing list pgsql-performance
Hello,
we noticed that in the presence of a schema with many partitions the jitting overhead penalizes the total query execution time so much that the planner should have decided not to jit at all. For example without jitting we go a 8.3 s execution time and with jitting enabled 13.8 s.
Attached you can find the TPC-h schema, a query to trigger it and the plans that we obtained.
Setup:
Current master from PSQL git repo, only compiled with llvm
TPC-h schema attached, plus a single index per table, and a scale factor of 10. Tables where analyzed.
The query is variation of query 12 to make the effect more relevant.
Max_workers_per_gather is 8
And we only vary the jit flag, we do not modify the costs.
Is this behavior expected? Is the cost function for jitting missing some circumstances?
Cheers
Luis
luis.carril@swarm64.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
Attachment
pgsql-performance by date: