Skip site navigation (1) Skip section navigation (2)

Re: write scalability

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: write scalability
Date: 2011-07-26 16:33:04
Message-ID: CABOikdNRMZCGTc3YrNMxpAnpYDxaBn9aNC0-X+upfyGyQHuvOw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Jul 26, 2011 at 12:29 PM, Pavan Deolasee
<pavan(dot)deolasee(at)gmail(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-07-26 16:55:29
Subject: Re: write scalability
Previous:From: Pavan DeolaseeDate: 2011-07-26 16:29:21
Subject: Re: write scalability

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group