From: Yeb Havinga <yebhavinga@gmail.com>
To: Samuel Gendler <sgendler@ideasculptor.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: write barrier question
Date: Wed, 18 Aug 2010 22:25:27 +0200
Message-ID: <4C6C41B7.4060709@gmail.com> (raw)
In-Reply-To: <AANLkTim0X2oZ61dzvwG_+TWf94DLEr_0Q_hecq57EZ6+@mail.gmail.com>
References: <AANLkTim0X2oZ61dzvwG_+TWf94DLEr_0Q_hecq57EZ6+@mail.gmail.com>
Samuel Gendler wrote:
> When running pgbench on a db which fits easily into RAM (10% of RAM =
> -s 380), I see transaction counts a little less than 5K. When I go to
> 90% of RAM (-s 3420), transaction rate dropped to around 1000 ( at a
> fairly wide range of concurrencies). At that point, I decided to
> investigate the performance impact of write barriers.
At 90% of RAM you're probable reading data as well, not only writing.
Watching iostat -xk 1 or vmstat 1 during a test should confirm this. To
find the maximum database size that fits comfortably in RAM you could
try out http://github.com/gregs1104/pgbench-tools - my experience with
it is that it takes less than 10 minutes to setup and run and after some
time you get rewarded with nice pictures! :-)
regards,
Yeb Havinga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: yebhavinga@gmail.com, sgendler@ideasculptor.com
Subject: Re: write barrier question
In-Reply-To: <4C6C41B7.4060709@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox