Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id DE7CB1E34FD7 for ; Wed, 23 Nov 2011 11:19:18 -0400 (AST) Received: from moutng.kundenserver.de ([212.227.126.186]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RTEbW-0002XM-Tt for pgsql-performance@postgresql.org; Wed, 23 Nov 2011 15:19:19 +0000 Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0M5850-1QeINT373W-00yfqI; Wed, 23 Nov 2011 16:19:06 +0100 Message-ID: <4ECD0EE8.5030401@2ndQuadrant.com> Date: Wed, 23 Nov 2011 10:19:04 -0500 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: SSD endurance calculations References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:+ryvLBsutN61LvV22NpgF2c+T7/TpjohRA9dxE8qfqF QbfrtO2Yse8YfnAymQi9/uNkanP0+x2NzF3ZN0ZsyGBDBLCyOh i03gOKjGomPHscgOroeV6/MZVGjdR9QhV+la5WVE3/5EVWcFky F93QCiwNBjqGhXQMX96GXJ58qNBMYEInhFs2mLGXrjzpCXAA5b OLcTh8CQWj/4VWaoSQK8f56TcpgHWCj2Xodd25HnfMeSfFZfQP CoAP52x0mtqO/0rX4qci6GeXyCvEHic3yI027AXkwswpBqwxlY 1NAfDc+BL83SrGjAuta/zVN9mpqi8PcDOsINaMnIWzkIjc/kI3 LGtKuwpjHt6+NI4niH6c= X-Archive-Number: 201111/258 X-Sequence-Number: 45769 On 11/21/2011 04:03 PM, Christiaan Willemsen wrote: > > Secondly, I also looked at the reliability figures of the Intel 320. > They show 5 years of 20GB per day, meaning that it will hold up for > about 200 days in our system. RAID 10 wil make 400 days of that, but > this seems hardly a lot.. Am I missing something here? > The 320 series drives are not intended for things that write as heavily as you do. If your database is growing fast enough that you're going to hit a terabyte in a short period of time, just cross that right off the list of possibilities. Intel's 710 series is the one aimed at your sort of workload. You can probably pull down the total write volume on your system by more aggressively running VACUUM FREEZE shortly after new data is loaded. PostgreSQL tends to write blocks even in INSERT-only tables several times; forcing them to freeze early can eliminate several of them. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us