From: Mark Kirkwood <markir@paradise.net.nz>
To: Brian Hurt <bhurt@janestcapital.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Easy read-heavy benchmark kicking around?
Date: Tue, 07 Nov 2006 14:52:09 +1300
Message-ID: <454FE6C9.7060404@paradise.net.nz> (raw)
In-Reply-To: <454F9F62.9070408@janestcapital.com>
References: <20061102160057.GA26580@oppetid.no>
<454F9F62.9070408@janestcapital.com>
Brian Hurt wrote:
> I'm having a spot of problem with out storage device vendor. Read
> performance (as measured by both bonnie++ and hdparm -t) is abysmal
> (~14Mbyte/sec), and we're trying to get them to fix it. Unfortunately,
> they're using the fact that bonnie++ is an open source benchmark to
> weasle out of doing anything- they can't fix it unless I can show an
> impact in Postgresql.
>
> So the question is: is there an easy to install and run, read-heavy
> benchmark out there that I can wave at them to get them to fix the
> problem? I have a second database running on a single SATA drive, so I
> can use that as a comparison point- "look, we're getting 1/3rd the read
> speed of a single SATA drive- this sucks!"
>
You could use the lineitem table from the TPC-H dataset
(http://www.tpc.org/tpch/default.asp).
Generate the dataset for a scale factor that makes lineitem about 2x
your ram, load the table and do:
SELECT count(*) FROM lineitem
vmstat or iostat while this is happening should display your meager
throughput well enough to get your vendors attention (I'm checking this
on a fairly old 4 disk system of mine as I type this - I'm seeing about
90Mb/s...)
best wishes
Mark
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: markir@paradise.net.nz, bhurt@janestcapital.com
Subject: Re: Easy read-heavy benchmark kicking around?
In-Reply-To: <454FE6C9.7060404@paradise.net.nz>
* 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