Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...) - Mailing list pgsql-performance

From Josh Berkus
Subject Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...)
Date
Msg-id 200410161418.26557.josh@agliodbs.com
Whole thread Raw
In response to Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...)
List pgsql-performance
Tom,

> We could also get rid of the linear search in UnlockBuffers().  The only
> thing it's for anymore is to release a BM_PIN_COUNT_WAITER flag, and
> since a backend could not be doing more than one of those at a time,
> we don't really need an array of flags for that, only a single variable.
> This does not show in the OSDL results, which I presume means that their
> test case is not exercising transaction aborts;

In the test, one out of every 100 new order transactions is aborted (about 1
out of 150 transactions overall).

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...)
Next
From: Tom Lane
Date:
Subject: Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...)