Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 9F0501337BDE for ; Tue, 29 Mar 2011 01:55:50 -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 65288-08 for ; Tue, 29 Mar 2011 04:55:43 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from shrek.krogh.cc (2605ds1-ynoe.0.fullrate.dk [90.184.12.24]) by mail.postgresql.org (Postfix) with ESMTP id 5EA601337B47 for ; Tue, 29 Mar 2011 01:55:43 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id 41806155963; Tue, 29 Mar 2011 06:55:41 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P41jJMkji12l; Tue, 29 Mar 2011 06:55:38 +0200 (CEST) Received: from [90.184.13.151] (2605ds1-ynoe.2.fullrate.dk [90.184.13.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jesper@krogh.cc) by shrek.krogh.cc (Postfix) with ESMTPSA id ECAA7151B67; Tue, 29 Mar 2011 06:55:37 +0200 (CEST) Message-ID: <4D916649.6030601@krogh.cc> Date: Tue, 29 Mar 2011 06:55:37 +0200 From: Jesper Krogh User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Merlin Moncure CC: Andy , "pgsql-performance@postgresql.org" , Greg Smith Subject: Re: Intel SSDs that may not suck References: <4D90EDB6.2080609@2ndQuadrant.com> <535760.62572.qm@web111307.mail.gq1.yahoo.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=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201103/347 X-Sequence-Number: 43026 On 2011-03-29 06:13, Merlin Moncure wrote: > My own experience with MLC drives is that write cycle expectations are > more or less as advertised. They do go down (hard), and have to be > monitored. If you are writing a lot of data this can get pretty > expensive although the cost dynamics are getting better and better for > flash. I have no idea what would be precisely prudent, but maybe some > good monitoring tools and phased obsolescence at around 80% duty cycle > might not be a bad starting point. With hard drives, you can kinda > wait for em to pop and swap em in -- this is NOT a good idea for flash > raid volumes. What do you mean by "hard", I have some in our setup, but havent seen anyting "hard" just yet. Based on report on the net they seem to slow down writes to "next to nothing" when they get used but that seems to be more gracefully than old rotating drives.. can you elaborate a bit more? Jesper -- Jesper