pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: pgsql-performance@postgresql.org
Subject: Re: Slow restoration question
Date: Wed, 3 May 2006 13:08:21 -0500
Message-ID: <20060503180821.GZ97354@pervasive.com> (raw)
In-Reply-To: <20060503170604.GP31328@mathom.us>
References: <622925BE-A31E-42FD-AF6A-68DDF3B4A1B7@clickspace.com>
	<1146595755.12053.111.camel@archimedes>
	<758B0591-3C9C-418B-9AF2-E962003C4904@rackspace.com>
	<20060502215329.GI97354@pervasive.com>
	<4A7F9950-65E0-4FA5-9FEC-BA1A93E615E5@clickspace.com>
	<20060503121847.GN31328@mathom.us>
	<30D5959B-3CCD-4CB4-B2D7-30DEA9F08BB6@torgo.978.org>
	<20060503155938.GO31328@mathom.us>
	<1146672434.22037.38.camel@state.g2switchworks.com>
	<20060503170604.GP31328@mathom.us>

On Wed, May 03, 2006 at 01:06:06PM -0400, Michael Stone wrote:
> On Wed, May 03, 2006 at 11:07:15AM -0500, Scott Marlowe wrote:
> >I have often used the mem=xxx arguments to lilo when needing to limit
> >the amount of memory for testing purposes.  Just google for limit memory
> >and your bootloader to find the options.
> 
> Or, just don't worry about it. Even if you get bonnie to reflect real 
> numbers, so what? In general the goal is to optimize application 
> performance, not bonnie performance. A simple set of dd's is enough to 
> give you a rough idea of disk performance, beyond that you really need 
> to see how your disk is performing with your actual workload.

Well, in this case the question was about random write access, which dd
won't show you.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (23+ messages)  latest in thread

Message-ID: <20060503180821.GZ97354@pervasive.com>
Permalink:  ../20060503180821.GZ97354@pervasive.com/
Also on:    postgresql.org/message-id/20060503180821.GZ97354@pervasive.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: jnasby@pervasive.com
  Subject: Re: Slow restoration question
  In-Reply-To: <20060503180821.GZ97354@pervasive.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