Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id BC1FC9FB1F5 for ; Mon, 6 Nov 2006 16:47:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 33298-08 for ; Mon, 6 Nov 2006 16:47:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from janestcapital.com (www.janestcapital.com [66.155.124.107]) by postgresql.org (Postfix) with ESMTP id 2E3DA9FB1F2 for ; Mon, 6 Nov 2006 16:47:31 -0400 (AST) Received: from [192.168.250.117] [209.213.205.130] by janestcapital.com with ESMTP (SMTPD32-8.13) id AF622CA500A4; Mon, 06 Nov 2006 15:47:30 -0500 Message-ID: <454F9F62.9070408@janestcapital.com> Date: Mon, 06 Nov 2006 15:47:30 -0500 From: Brian Hurt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Easy read-heavy benchmark kicking around? References: <20061102160057.GA26580@oppetid.no> In-Reply-To: <20061102160057.GA26580@oppetid.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.008 tagged_above=0 required=5 tests=AWL, BAYES_40 X-Spam-Level: X-Archive-Number: 200611/72 X-Sequence-Number: 21842 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!" Any advice? Brian