Re: testing ProcArrayLock patches

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: testing ProcArrayLock patches
Date: 2011-11-18 18:14:56
Message-ID: 4EC64C400200002500043239@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> Yeah, I'd just drop -S.

Easily done.

> Make sure to use -c N -j N with pgbench, or you'll probably not be
> able to saturate it.

Yeah, that's part of the script I copied from you.

> I've also had good luck with wal_writer_delay=20ms, although if
> you have synchronous_commit=on that might not matter, and it's
> much less important since Simon's recent patch in that area went
> in.

What the heck; will do.

> What scale factor are you testing at?

100. Perhaps I should boost that since I'm going as far as 128
clients?

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2011-11-18 18:31:56 Re: FlexLocks
Previous Message Pavel Stehule 2011-11-18 18:13:36 Re: proposal: better support for debugging of overloaded functions