Re: write scalability - Mailing list pgsql-hackers

From Robert Haas
Subject Re: write scalability
Date
Msg-id CA+TgmoYiPqrBQrJ3PBytJrN=d6RQR+KFxB33=Sct9nqDmC6rRg@mail.gmail.com
Whole thread Raw
In response to Re: write scalability  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Responses Re: write scalability
List pgsql-hackers
On Tue, Jul 26, 2011 at 11:40 AM, Pavan Deolasee
<pavan.deolasee@gmail.com> wrote:
> On Tue, Jul 26, 2011 at 9:07 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Mon, Jul 25, 2011 at 10:14 PM, Greg Smith <greg@2ndquadrant.com> wrote:
>>> On 07/25/2011 04:07 PM, Robert Haas wrote:
>>>>
>>>> I did 5-minute pgbench runs with unlogged tables and with permanent
>>>> tables, restarting the database server and reinitializing the tables
>>>> between each run.
>>>
>>> Database scale?  One or multiple pgbench worker threads?  A reminder on the
>>> amount of RAM in the server would be helpful for interpreting the results
>>> too.
>>
>> Ah, sorry.  scale = 100, so small.  pgbench invocation is:
>>
>
> It might be worthwhile to test only with the accounts and history
> table and also increasing the number of statements in a transaction.
> Otherwise the tiny tables can quickly become a bottleneck.

What kind of bottleneck?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Another issue with invalid XML values
Next
From: David Fetter
Date:
Subject: Re: vacuumlo patch