Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 94D1B63319E for ; Thu, 8 Jul 2010 18:43:21 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 24541-04 for ; Thu, 8 Jul 2010 21:43:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from skunk.mtbrook.bozemanpass.com (skunk.mtbrook.bozemanpass.com [69.145.82.195]) by mail.postgresql.org (Postfix) with ESMTP id 9AD4B632ED6 for ; Thu, 8 Jul 2010 18:43:13 -0300 (ADT) Received: from [69.145.82.252] (unknown [69.145.82.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skunk.mtbrook.bozemanpass.com (Postfix) with ESMTP id CA5FE558039 for ; Thu, 8 Jul 2010 15:54:31 -0700 (PDT) Message-ID: <4C364671.7010109@boreham.org> Date: Thu, 08 Jul 2010 15:43:13 -0600 From: David Boreham User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 CC: pgsql-performance@postgresql.org Subject: Re: performance on new linux box References: <4C3532CC.6070601@squeakycode.net> <4C3591F40200002500033219@gw.wicourts.gov> <4C35A23B0200002500033220@gw.wicourts.gov> <4C360677.1090608@emolecules.com> <95971335.20100708211351@erwied.eu> <488953776.20100708213233@erwied.eu> <4C35E4CA020000250003327E@gw.wicourts.gov> <4C363CAE.7010401@emolecules.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.879 tagged_above=-10 required=5 tests=BAYES_00=-1.9, MISSING_HEADERS=1.021 X-Spam-Level: X-Archive-Number: 201007/140 X-Sequence-Number: 39529 On 7/8/2010 3:18 PM, Timothy.Noonan@emc.com wrote: > How does the linux machine know that there is a BBU installed and to > change its behavior or change the behavior of Postgres? I am > experiencing performance issues, not with searching but more with IO. > It doesn't change its behavior at all. It's in the business of writing stuff to a file and waiting until that stuff has been put on the disk (it wants a durable write). What the write buffer/cache does is to inform the OS, and hence PG, that the write has been done when in fact it hasn't (yet). So the change in behavior is only to the extent that the application doesn't spend as much time waiting.