Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 6CFF3632724 for ; Mon, 9 Aug 2010 19:42:11 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 90457-04 for ; Mon, 9 Aug 2010 22:42:04 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qw0-f46.google.com (mail-qw0-f46.google.com [209.85.216.46]) by mail.postgresql.org (Postfix) with ESMTP id 0BE846325E6 for ; Mon, 9 Aug 2010 19:42:03 -0300 (ADT) Received: by qwh6 with SMTP id 6so7696404qwh.19 for ; Mon, 09 Aug 2010 15:42:02 -0700 (PDT) Received: by 10.224.57.193 with SMTP id d1mr9062517qah.110.1281393722696; Mon, 09 Aug 2010 15:42:02 -0700 (PDT) Received: from [10.10.3.129] (71-6-94-66.static-ip.telepacific.net [71.6.94.66]) by mx.google.com with ESMTPS id q8sm4353906qcs.36.2010.08.09.15.42.00 (version=SSLv3 cipher=RC4-MD5); Mon, 09 Aug 2010 15:42:01 -0700 (PDT) Subject: Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD From: Jeff Davis To: Scott Carey Cc: Michael March , "pgsql-performance@postgresql.org" In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Date: Mon, 09 Aug 2010 15:41:59 -0700 Message-ID: <1281393719.3667.8.camel@jdavis-ux.asterdata.local> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 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, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201008/102 X-Sequence-Number: 39945 On Mon, 2010-08-09 at 09:49 -0700, Scott Carey wrote: > Also, the amount of data at risk in a power loss varies between > drives. For Intel's drives, its a small chunk of data ( < 256K). For > some other drives, the cache can be over 30MB of outstanding writes. > For some workloads this is acceptable -- not every application is > doing financial transactions. Not every part of the system needs to > be on an SSD either -- the WAL, and various table spaces can all have > different data integrity and performance requirements. I don't think it makes sense to speak about the data integrity of a drive in terms of the amount of data at risk, especially with a DBMS. Depending on which 256K you lose, you might as well lose your entire database. That may be an exaggeration, but the point is that it's not as simple as "this drive is only risking 256K data loss per outage". Regards, Jeff Davis