Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 23454B5DBEA for ; Wed, 24 Aug 2011 17:11:42 -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 46942-03 for ; Wed, 24 Aug 2011 20:11:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.postgresql.org (Postfix) with ESMTP id 541F9B5DBDC for ; Wed, 24 Aug 2011 17:11:35 -0300 (ADT) Received: from [192.168.1.7] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LehC6-1RbiHI0sj0-00qSah; Wed, 24 Aug 2011 22:11:34 +0200 Message-ID: <4E555AF5.4080202@2ndQuadrant.com> Date: Wed, 24 Aug 2011 16:11:33 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110702 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Intel 320 SSD info References: <4E552DCF.80802@boreham.org> <1314206629.63488.YahooMailNeo@web111301.mail.gq1.yahoo.com> <4E5537C9.9080308@2ndQuadrant.com> <4E5537F6.3070105@boreham.org> In-Reply-To: <4E5537F6.3070105@boreham.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:6gVxOedAu/kGHkoYw5AIJ8WK09/2kzP/IkrR8nYgtsI SjzBS4oejSjKXSyPBEY3HkVLRgtSlq/FJqHrKHDThXdSFJfjAj gSFUJ7K61H4N4MAd6uy6UzrxeM7Lall/FgT2oMG7+MnBw9za+R 4EsZT4YmBIJNybHCtEANzs4YkpIt9XbXhfC3Dl/RN3MIigPoBI SKTaBM+NlrYpas9okRdxjeWI2h+j/pK3zXv5bTHKi0= 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: 201108/288 X-Sequence-Number: 44735 On 08/24/2011 01:42 PM, David Boreham wrote: > On 8/24/2011 11:41 AM, Greg Smith wrote: >> >> >> I've measured the performance of this drive from a couple of >> directions now, and it always comes out the same. For PostgreSQL, >> reading or writing 8K blocks, I'm seeing completely random workloads >> hit a worst-case of 20MB/s; that's just over 2500 IOPS. It's quite >> possible that number can go lower under pressure of things like >> internal drive garbage collection however, which I believe is going >> into the 600 IOPS figure. I haven't tried to force that yet--drive >> is too useful to me to try and burn it out doing tests like that at >> the moment. > > I hope someone from Intel is reading -- it would be well worth their > while to just send you a few drives, > since you are set up to perform the right test, and can provide > impartial results. Don't worry, they are. With the big firmware bug in the 320 series lingering over things, it wasn't really worth wandering down that road yet until this week. Now that they can ship me drives that are expected to work, I can pick back up work on performance testing them. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us