X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id F06F79FA372
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed,  3 May 2006 13:07:23 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 78682-04
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed,  3 May 2006 13:07:16 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from exchange.g2switchworks.com (mail.g2switchworks.com
	[63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 51F829F9C10
	for <pgsql-performance@postgresql.org>;
	Wed,  3 May 2006 13:07:16 -0300 (ADT)
Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com
	([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ;
	Wed,  3 May 2006 16:07:15 +0000
Received: from state.g2switchworks.com by mail.g2switchworks.com;
	03 May 2006 11:07:15 -0500
Subject: Re: Slow restoration question
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Michael Stone <mstone+postgres@mathom.us>
Cc: Jeff Trout <threshar@torgo.978.org>, pgsql-performance@postgresql.org
In-Reply-To: <20060503155938.GO31328@mathom.us>
References: <444F24E9.2010907@lisasoft.com>
	<20060502171617.GZ97354@pervasive.com>
	<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>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1146672434.22037.38.camel@state.g2switchworks.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Wed, 03 May 2006 11:07:15 -0500
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200605/87
X-Sequence-Number: 18874

On Wed, 2006-05-03 at 10:59, Michael Stone wrote:
> On Wed, May 03, 2006 at 09:19:52AM -0400, Jeff Trout wrote:
> >Bonnie++ is able to use very large datasets. It also tries to figure  
> >out hte size you want (2x ram) - the original bonnie is limited to 2GB.
> 
> Yes, and once you get into large datasets like that the quality of the 
> data is fairly poor because the program can't really eliminate cache 
> effects. IOW, it tries but (in my experience) doesn't succeed very well.

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.