pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Yeb Havinga <yebhavinga@gmail.com>
To: Chris Hoover <revoohc@gmail.com>
Cc: PGSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Benchmarking a large server
Date: Tue, 10 May 2011 08:58:21 +0200
Message-ID: <4DC8E20D.7090602@gmail.com> (raw)
In-Reply-To: <BANLkTikONPZ_7zQNfbyyN4MGBnn5PXHrAg@mail.gmail.com>
References: <BANLkTikONPZ_7zQNfbyyN4MGBnn5PXHrAg@mail.gmail.com>

On 2011-05-09 22:32, Chris Hoover wrote:
>
> The issue we are running into is how do we benchmark this server, 
> specifically, how do we get valid benchmarks for the Fusion IO card? 
>  Normally to eliminate the cache effect, you run iozone and other 
> benchmark suites at 2x the ram.  However, we can't do that due to 2TB 
> > 1.3TB.
>
> So, does anyone have any suggestions/experiences in benchmarking 
> storage when the storage is smaller then 2x memory?

Oracle's Orion test tool has a configurable cache size parameter - it's 
a separate download and specifically written to benchmark database oltp 
and olap like io patterns, see 
http://www.oracle.com/technetwork/topics/index-089595.html

-- 
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data




view thread (20+ messages)  latest in thread

Message-ID: <4DC8E20D.7090602@gmail.com>
Permalink:  ../4DC8E20D.7090602@gmail.com/
Also on:    postgresql.org/message-id/4DC8E20D.7090602@gmail.com

 · 

reply

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, revoohc@gmail.com
  Subject: Re: Benchmarking a large server
  In-Reply-To: <4DC8E20D.7090602@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