Re: Why JIT speed improvement is so modest? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why JIT speed improvement is so modest?
Date
Msg-id CA+TgmoYewAaYNQFALyTCTaBuGW0uay0+wHkEGaQAwaPK1PkZ1Q@mail.gmail.com
Whole thread Raw
In response to Re: Why JIT speed improvement is so modest?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Why JIT speed improvement is so modest?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
On Thu, Nov 28, 2019 at 2:08 AM Konstantin Knizhnik
<k.knizhnik@postgrespro.ru> wrote:
> calls float4_accum for each row of T, the same query in VOPS will call
> vops_float4_avg_accumulate for each tile which contains 64 elements.
> So vops_float4_avg_accumulate is called 64 times less than float4_accum.
> And inside it contains straightforward loop:
>
>              for (i = 0; i < TILE_SIZE; i++) {
>                  sum += opd->payload[i];
>              }
>
> which can be optimized by compiler (loop unrolling, use of SIMD
> instructions,...).

Part of the reason why the compiler can optimize that so well is
probably related to the fact that it includes no overflow checks.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [Proposal] Level4 Warnings show many shadow vars
Next
From: Justin Pryzby
Date:
Subject: Re: error context for vacuum to include block number