From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "P(dot) Joshua Rovero" <rovero(at)sonalysts(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.4b1 vs 7.3.4 performance |
Date: | 2003-08-26 22:55:06 |
Message-ID: | 24105.1061938506@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"P. Joshua Rovero" <rovero(at)sonalysts(dot)com> writes:
>>> Ran sets of 150 pgbench runs, with clients (1, 2, 4, 8, 16) and
>>> transactions (5 each at 125, 250, 500, 1000, 2000, 4000),
>>
>> BTW, what was the pgbench "scale factor"?
> 1 for these cases.
Hm. You really want scale factor >= number of clients, else you will
mostly be measuring the effects of contention. The scale factor is the
same as the number of rows created in the "branches" table, and every
transaction wants to update one of the "branches" rows. So if you have
just one branch, all the clients try to update that same row every time,
effectively serializing their transactions.
I now suspect that what you measured is just some marginal improvement
we made in the lock manager. Not sure what, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Grant Succeeded | 2003-08-27 00:02:56 | Re: Decent VACUUM (was: Buglist) |
Previous Message | P. Joshua Rovero | 2003-08-26 22:47:35 | Re: 7.4b1 vs 7.3.4 performance |