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 0A7A99F9CC1 for ; Wed, 3 May 2006 15:08:36 -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 88233-01 for ; Wed, 3 May 2006 15:08:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 7CE789F9C1D for ; Wed, 3 May 2006 15:08:23 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id BBB3656435; Wed, 3 May 2006 13:08:22 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Wed, 3 May 2006 13:08:21 -0500 Date: Wed, 3 May 2006 13:08:21 -0500 From: "Jim C. Nasby" To: pgsql-performance@postgresql.org Subject: Re: Slow restoration question Message-ID: <20060503180821.GZ97354@pervasive.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060503170604.GP31328@mathom.us> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060503:pgsql-performance@postgresql.org::tnx6cwDThb/cJOQk:00000 000000000000000000000000CMwE X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/91 X-Sequence-Number: 18878 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