Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 0DA05633A6C for ; Thu, 12 Aug 2010 04:29:12 -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 24351-02 for ; Thu, 12 Aug 2010 07:29:04 +0000 (UTC) X-Greylist: delayed 00:06:40.565108 by SQLgrey-1.7.6 Received: from adonis.tweakers.net (adonis.tweakers.net [213.239.154.11]) by mail.postgresql.org (Postfix) with ESMTP id B5C6C633A68 for ; Thu, 12 Aug 2010 04:29:04 -0300 (ADT) Received: from [192.168.1.33] (82-169-23-111.ip.telfort.nl [82.169.23.111]) by adonis.tweakers.net (Postfix) with ESMTPSA id D616D20D8A for ; Thu, 12 Aug 2010 09:22:21 +0200 (CEST) Message-ID: <4C63A12B.7050607@tweakers.net> Date: Thu, 12 Aug 2010 09:22:19 +0200 From: Arjen van der Meijden User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD References: <20100811205356.AHB77050@ms14.lnh.mail.rcn.net> In-Reply-To: <20100811205356.AHB77050@ms14.lnh.mail.rcn.net> 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=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/142 X-Sequence-Number: 39985 On 12-8-2010 2:53 gnuoytr@rcn.com wrote: > - The value of SSD in the database world is not as A Faster HDD(tm). > Never was, despite the naive' who assert otherwise. The value of SSD > is to enable BCNF datastores. Period. If you're not going to do > that, don't bother. Silicon storage will never reach equivalent > volumetric density, ever. SSD will never be useful in the byte bloat > world of xml and other flat file datastores (resident in databases or > not). Industrial strength SSD will always be more expensive/GB, and > likely by a lot. (Re)factoring to high normalization strips out an > order of magnitude of byte bloat, increases native data integrity by > as much, reduces much of the redundant code, and puts the ACID where > it belongs. All good things, but not effortless. It is actually quite common to under-utilize (short stroke) hard drives in the enterprise world. Simply because 'they' need more IOps per amount of data than a completely utilized disk can offer. As such the expense/GB can be much higher than simply dividing the capacity by its price (and if you're looking at fiber channel disks, that price is quite high already). And than it is relatively easy to find enterprise SSD's with better pricing for the whole system as soon as the IOps are more important than the capacity. So in the current market, you may already be better off, price-wise, with (expensive) SSD if you need IOps rather than huge amounts of storage. And while you're in both cases not comparing separate disks to SSD, you're replacing a 'disk based storage system' with a '(flash) memory based storage system' and it basically becomes 'A Faster HDD' ;) But you're right, that for data-heavy applications, completely replacing HDD's with some form of SSD is not going to happen soon, maybe never. Best regards, Arjen