Received: from maia.hub.org (unknown [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id AD4AD1337990 for ; Sat, 23 Oct 2010 18:03:25 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 15175-10 for ; Sat, 23 Oct 2010 21:03:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [69.36.227.170]) by mail.postgresql.org (Postfix) with ESMTP id E45391336705 for ; Sat, 23 Oct 2010 18:03:17 -0300 (ADT) Received: from adsl-63-195-55-98.dsl.snfc21.pacbell.net ([63.195.55.98] helo=[192.168.47.100]) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1P9lFB-00022d-FD for pgsql-performance@postgresql.org; Sat, 23 Oct 2010 14:03:16 -0700 Message-ID: <4CC34D8A.4050606@agliodbs.com> Date: Sat, 23 Oct 2010 14:03:06 -0700 From: Josh Berkus User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100217 Shredder/3.0.3pre MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: BBU Cache vs. spindles References: <4CC04EA50200002500036C5E@gw.wicourts.gov> <201010211935.o9LJZTM21744@momjian.us> <4CC0513E0200002500036C68@gw.wicourts.gov> <4CC1094C.1090306@2ndquadrant.com> <13038.1287720327@sss.pgh.pa.us> <4CC1AFB3.3000903@2ndquadrant.com> <4CC183610200002500036CDC@gw.wicourts.gov> <4CC19A330200002500036CF8@gw.wicourts.gov> In-Reply-To: <4CC19A330200002500036CF8@gw.wicourts.gov> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201010/390 X-Sequence-Number: 40808 > Even if it's possible, it's far from clear to me that it would be an > improvement. The author estimates (apparently somewhat loosely) > that it's a 5% to 10% performance hit in InnoDB; I'm far from > certain that full_page_writes cost us that much. Does anyone have > benchmark numbers handy? It most certainly can, depending on your CPU saturation and I/O support. I've seen a 10% improvement in througput time from turning off full_page_writes on some machines, such as when we were doing the SpecJAppserver benchmarks on Solaris. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com