Re: testing ProcArrayLock patches
От | Pavan Deolasee |
---|---|
Тема | Re: testing ProcArrayLock patches |
Дата | |
Msg-id | CABOikdNs=6zK0sTQu+xmLeaQPL5kk8hzzV19oqW=gTheST-D1A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: testing ProcArrayLock patches ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: testing ProcArrayLock patches
Re: testing ProcArrayLock patches |
Список | pgsql-hackers |
On Mon, Nov 21, 2011 at 10:44 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > "Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote: > >> I can run one more set of tests tonight before I have to give it >> back to the guy who's putting it into production. It sounds like >> a set like the above except with synchronous_commit = off might be >> desirable? > > OK, that's what I did. This gave me my best numbers yet for an > updating run of pgbench: tps = 38039.724212 for prepared statements > using the flexlock patch. This patch is a clear win when you get to > 16 clients or more. > 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 Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: