From: Greg Smith <gsmith@gregsmith.com>
To: Jeffrey Baker <jwbaker@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Practical upper limits of pgbench read/write tps with 8.3
Date: Mon, 7 Jul 2008 18:22:05 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0807071803150.13336@westnet.com> (raw)
In-Reply-To: <fd145f7d0807071405t1bdf4be0j8583fc9965a7719e@mail.gmail.com>
References: <fd145f7d0807071405t1bdf4be0j8583fc9965a7719e@mail.gmail.com>
On Mon, 7 Jul 2008, Jeffrey Baker wrote:
> On the single 2.2GHz Athlon, the maximum tps seems to be 1450...what's
> the bottleneck? Is PG lock-bound?
It can become lock-bound if you don't make the database scale
significantly larger than the number of clients, but that's probably not
your problem. The pgbench client driver program itself is pretty CPU
intensive and can suffer badly from kernel issues. I am unsurprised you
can only hit 1450 with a single CPU. On systems with multiple CPUs where
the single CPU running the pgbench client is much faster than your 2.2GHz
Athlon, you'd probably be able to get a few thousand TPS, but eventually
the context switching of the client itself can become a bottleneck.
Running pgbench against a RAM disk is a good way to find out where the
system bottlenecks at without disk I/O involvement, you might try that
test on your larger server when you get a chance. One interesting thing
to watch you may not have tried yet is running top and seeing how close to
a single CPU pgbench itself is running at. If you've got 4 CPUs, and the
pgbench client program shows 25% utilization, it is now the bottleneck
rather than whatever you thought you were measuring. I thought this might
be the case in the last test results you reported on Friday but didn't
have a chance to comment on it until now.
One thing you can try here is running pgbench itself on another server
than the one hosting the database, but that seems to top out at a few
thousand TPS as well; may get higher than you've been seeing though.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com, jwbaker@gmail.com
Subject: Re: Practical upper limits of pgbench read/write tps with 8.3
In-Reply-To: <Pine.GSO.4.64.0807071803150.13336@westnet.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