From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: write scalability |
Date: | 2011-07-26 02:14:21 |
Message-ID: | 4E2E22FD.8040503@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
The other thing I'd recommend if you're running more write-heavy tests
is to turn off autovacuum. Whether or not it kicks in depends on the
test duration and the TPS rate, which adds a source of variability
better avoided here. It also means that faster tests end up getting
penalized by having it run near their end, which makes them no longer
look like fast results.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Kupershmidt | 2011-07-26 02:29:29 | Re: psql: bogus descriptions displayed by \d+ |
Previous Message | Robert Haas | 2011-07-26 01:41:53 | Re: write scalability |