Re: Avoiding repeated snapshot computation

Поиск
Список
Период
Сортировка
От Ants Aasma
Тема Re: Avoiding repeated snapshot computation
Дата
Msg-id CA+CSw_u1Pv37wn8ovfH0D3yq8dsXV1qxrfzJqPzE1H3G3hXKPQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Avoiding repeated snapshot computation  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Список pgsql-hackers
On Tue, Nov 29, 2011 at 7:12 AM, Pavan Deolasee
<pavan.deolasee@gmail.com> wrote:
> I think that a good idea. We need a representation that needs minimum
> processing to derive the snapshot.

I was looking over the generated code for GetSnapshotData to see if there
is any low hanging fruit for micro-optimization. The assembly mostly looks
pretty tight, but there are 3 function calls to TransactionIdPrecedes and
TransactionIdFollowsOrEquals. All the parameters are known to be normal
xids, so there are duplicated checks for that and a lot of movs for the calling
convention. I wonder if replacing them with special case macros would be
a good idea. In that case the whole check will compile down to one cmp
instruction. I'm running a set of benchmarks now on my laptop, but I guess
the difference will mostly become noticeable on beefier hardware when
ProcArray lock is heavily contended. Attached is a patch, if anyone wishes
to give it a go.

--
Ants Aasma

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Patch - Debug builds without optimization
Следующее
От: Tom Lane
Дата:
Сообщение: Re: autovacuum and default_transaction_isolation