On Tue, Jul 26, 2011 at 4:40M, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> wrote:
> On Tue, Jul 26, 2011 at 9:07 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Mon, Jul 25, 2011 at 10:14 PM, Greg Smith <greg(at)2ndquadrant(dot)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
>> 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.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2011-07-26 17:24:10|
|Subject: Re: WIP: Fast GiST index build|
|Previous:||From: Pavan Deolasee||Date: 2011-07-26 16:33:04|
|Subject: Re: write scalability|