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 906F19F9C1D for ; Wed, 3 May 2006 14:06: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 90814-04 for ; Wed, 3 May 2006 14:06:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by postgresql.org (Postfix) with ESMTP id 2A1E79F9CC1 for ; Wed, 3 May 2006 14:06:10 -0300 (ADT) Received: from osgiliath.mathom.us ([70.108.132.172]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IYP00HPI8U8R1KL@vms046.mailsrvcs.net> for pgsql-performance@postgresql.org; Wed, 03 May 2006 12:06:09 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by osgiliath.mathom.us (Postfix) with ESMTP id ECCED6EC9D for ; Wed, 03 May 2006 13:06:06 -0400 (EDT) Received: from osgiliath.mathom.us ([127.0.0.1]) by localhost (osgiliath.home.mathom.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16233-05-5 for ; Wed, 03 May 2006 13:06:06 -0400 (EDT) Received: by osgiliath.mathom.us (Postfix, from userid 1000) id 4487A6ECBE; Wed, 03 May 2006 13:06:06 -0400 (EDT) Date: Wed, 03 May 2006 13:06:06 -0400 From: Michael Stone Subject: Re: Slow restoration question In-reply-to: <1146672434.22037.38.camel@state.g2switchworks.com> To: pgsql-performance@postgresql.org Mail-followup-to: pgsql-performance@postgresql.org Message-id: <20060503170604.GP31328@mathom.us> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-disposition: inline X-Pgp-Fingerprint: 53 FF 38 00 E7 DD 0A 9C 84 52 84 C5 EE DF 7C 88 X-Virus-Scanned: Debian amavisd-new at mathom.us References: <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> <1146672434.22037.38.camel@state.g2switchworks.com> User-Agent: Mutt/1.5.11+cvs20060403 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/88 X-Sequence-Number: 18875 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. Mike Stone