On Tue, Jul 26, 2011 at 12:29 PM, Pavan Deolasee <pavan.deola...@gmail.com> wrote:
> > So many transactions trying to update a small set of rows in a table. > Is that what we really want to measure ? My thinking is that we might > see different result if they are updating different parts of the table > and the transaction start/stop overhead is spread across few > statements. > I think what I am suggesting is that the default pgbench test setup would probably not give you a good scalability as number of clients are increased and one reason could be the contention in the small table. So it might be a good idea to get rid of that and see if we get much better scalability and understand other bottlenecks. Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
