Обсуждение: Small optimization set tuple block/tableOid once

Поиск
Список
Период
Сортировка

Small optimization set tuple block/tableOid once

От
Ranier Vilela
Дата:
Hi.

Inspired by [1]
There is an opportunity for optimization according to the commit:
" Due to splitting the block id into two 16 bit integers, BlockIdSet() is more expensive than one might think. Doing it once per returned tuple shows up as a small but reliably reproducible cost. It's simple enough to set the block number just once per block in pagemode, so do so."

By moving the invariants out of the loop, it really is an improvement.

Then the following sources can be optimized:
contrib/pg_visibility/pg_visibility.c
contrib/pgstattuple/pgstatapprox.c
src/backend/access/heap/heapam.c
src/backend/access/heap/heapam_handler.c
src/backend/access/heap/pruneheap.c
src/backend/access/heap/vacuumlazy.c
src/backend/commands/dbcommands.c

Attached all patchs.

best regards,
Ranier Vilela

Вложения

Re: Small optimization set tuple block/tableOid once

От
Ranier Vilela
Дата:
rebased heapam.c and heapam_handler.c

best regards,
Ranier Vilela
Вложения