Re: testing ProcArrayLock patches - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: testing ProcArrayLock patches
Date
Msg-id CABOikdPBk3aVZaB+4etkA-mbnfMaQF2ZX5S5bOG5vsn=Og+27w@mail.gmail.com
Whole thread Raw
In response to Re: testing ProcArrayLock patches  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Mon, Nov 21, 2011 at 11:01 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Pavan Deolasee <pavan.deolasee@gmail.com> wrote:
>
>> It will be a great help if you could spare few minutes to also
>> test the patch to take out the frequently accessed PGPROC members
>> to a different array. We are seeing good improvements on HPUX IA
>> platform and the AMD Opteron and it will be interesting to know
>> what happens on the Intel platform too.
>>
>>
> http://archives.postgresql.org/message-id/4EB7C4C9.9070309@enterprisedb.com
>
> It's going to be hard to arrange more of the 20-hours runs I've been
> doing, but I can work in some more abbreviated tests.  What would be
> the best test for this?  (I would hate to try and find out I didn't
> exercise the right code path.)
>

I think 2-3 runs with 32 and 128 clients each with prepared statements
should suffice to quickly compare with the other numbers you posted
for the master.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: testing ProcArrayLock patches
Next
From: Joshua Berkus
Date:
Subject: Re: ISN was: Core Extensions relocation