Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id BE34C2E0062 for ; Thu, 3 Apr 2008 01:36:54 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 31749-05 for ; Thu, 3 Apr 2008 01:36:50 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by developer.postgresql.org (Postfix) with ESMTP id 56EE02E002D for ; Thu, 3 Apr 2008 01:36:51 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 22so2520114fge.23 for ; Wed, 02 Apr 2008 21:36:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=mcl53tmLSIzuLunN89ccqtMYIIuI7yGmWfabmIIfiGw=; b=qnh6fO1dy/YkhuhGkGYGPvVq3KB/44uB5reWnlzavMzo4fnUvw7ZHyMd26CpmFxrWfTz8iBt48gSH0LwOfToxI46iS585bTGg1qsLVpnh0t1zBX45lSpavj/AfpTgzgGsaxmHDLdGNsBr79VwkGvKskcZwDcfQYL6kB7jenrfao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ffOZZZpg31MFPZT+0RMDBrtaTxyj0QPq5DYAU1I0WV+Z8o+yuhTwh2+0Nxl6DN06tqb3EV5FLcDuwz+VJJXq1HCqYBvA357z8MjVnCCy1HgqDh7QITZuPJP+Y8zDgMrcE91X5hYgF7XvzuwC/tp5dEjHUJEg0vJ9zNTM6Rv4DPY= Received: by 10.82.123.8 with SMTP id v8mr24689876buc.30.1207197410095; Wed, 02 Apr 2008 21:36:50 -0700 (PDT) Received: by 10.82.145.1 with HTTP; Wed, 2 Apr 2008 21:36:50 -0700 (PDT) Message-ID: Date: Wed, 2 Apr 2008 23:36:50 -0500 From: "Merlin Moncure" To: "James Mansion" Subject: Re: SSDs Cc: pgsql-performance@postgresql.org In-Reply-To: <47F324B4.6010404@mansionfamily.plus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47F324B4.6010404@mansionfamily.plus.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/26 X-Sequence-Number: 29519 On Wed, Apr 2, 2008 at 1:16 AM, James Mansion wrote: > Tried harder to find info on the write cycles: found som CFs that claim > 2million > cycles, and found the Mtron SSDs which claim to have very advanced wear > levelling and a suitably long lifetime as a result even with an > assumption that > the underlying flash can do 100k writes only. > > The 'consumer' MTrons are not shabby on the face of it and not too > expensive, > and the pro models even faster. > > But ... the spec pdf shows really hight performance for average access, > stream > read *and* write, random read ... and absolutely pants performance for > random > write. Like 130/s, for .5k and 4k writes. > > Its so pants it looks like a misprint and it doesn't seem to square with the > review on tomshardware: > http://www.tomshardware.com/2007/11/21/mtron_ssd_32_gb/page7.html > > Even there, the database IO rate does seem lower than you might hope, > and this *might* be because the random reads are very very fast and the > random writes ... aren't. Which is a shame, because that's exactly the > bit I'd hope was fast. > > So, more work to do somewhere. if flash ssd random write was as good as random read, a single flash ssd could replace a stack of 15k disks in terms of iops (!). unfortunately, the random write performance of flash SSD is indeed grim. there are some technical reasons for this that are basically fundamental tradeoffs in how flash works, and the electronic processes involved. unfortunately even with 10% write 90% read workloads this makes flash a non-starter for 'OLTP' systems (exactly the sort of workloads you would want the super seek times). a major contributing factor is that decades of optimization and research have gone into disk based sytems which are pretty similar in terms of read and write performance. since flash just behaves differently, these optimizations read this paper for a good explanation of this [pdf]: http://tinyurl.com/357zux my personal opinion is these problems will prove correctable due to improvements in flash technology, improvement of filesystems and raid controllers in terms of flash, and introduction of other non volatile memory. so the ssd is coming...it's inevitable, just not as soon as some of us had hoped. merlin