From: Jeffrey Baker <jwbaker@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Practical upper limits of pgbench read/write tps with 8.3
Date: Mon, 7 Jul 2008 14:05:37 -0700
Message-ID: <fd145f7d0807071405t1bdf4be0j8583fc9965a7719e@mail.gmail.com> (raw)
I'm spending a third day testing with the ioDrive, and it occurred to
me that I should normalize my tests by mounting the database on a
ramdisk. The results were surprisingly low. On the single 2.2GHz
Athlon, the maximum tps seems to be 1450. This is achieved with a
single connection. I/O rates to and from the ramdisk never exceed
50MB/s on a one-minute average.
With the flash device on the same benchmark, the tps rate is 1350,
meaning that as far as PostgreSQL is concerned, on this machine, the
flash device achieves 90% of the best possible performance.
Question being: what's the bottleneck? Is PG lock-bound?
-jwb
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: jwbaker@gmail.com
Subject: Re: Practical upper limits of pgbench read/write tps with 8.3
In-Reply-To: <fd145f7d0807071405t1bdf4be0j8583fc9965a7719e@mail.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