Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ffpZ0-0004vX-J7 for pgsql-performance@arkaria.postgresql.org; Wed, 18 Jul 2018 16:44:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ffpYy-00042x-To for pgsql-performance@arkaria.postgresql.org; Wed, 18 Jul 2018 16:44:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ffpYy-00042q-7l for pgsql-performance@lists.postgresql.org; Wed, 18 Jul 2018 16:44:28 +0000 Received: from resqmta-ch2-11v.sys.comcast.net ([2001:558:fe21:29:69:252:207:43]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ffpYq-0003rg-9J for pgsql-performance@postgresql.org; Wed, 18 Jul 2018 16:44:24 +0000 Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id fnFPfixMzZ6PIfpYifS9Rd; Wed, 18 Jul 2018 16:44:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1531932252; bh=yR1WRHhMWidGwYHziL5LcyKYqkmtU5C8ilLmObiCBCQ=; h=Received:Received:To:From:Subject:Message-ID:Date:MIME-Version: Content-Type; b=Uncgr6yYxCm2C18fTTCaho4uH5PlKxCPl1vPYxt0TBHhs6PKiLe7hyr3vG1+mfVsi MtiyReEDtxzBJcyjbW/5yWPSzbtNLLqDlUQZmUyVT66FEwt0zY8EM9n8FWoCQWwChd URhuLcPBMLTBa+vsexzVimrkhUw831aoQgmhe7fqipp7zLCdv1i6Q4DfvLXkU1nGj6 kFgIqVetK657TJmS9bW10ZVrc0MzehxXvxTWPrx7RuwIpiDAfLn6EET/uSJHowcdTI MufWZOZ2JIVqC26S+LrijR4O0MMca7yoslhMTDKsbeBEQ4fGyv/J8eQlYyXffbk9o+ jKaWoVoiAbhHg== Received: from [IPv6:2601:19c:4701:878e:855:be56:282c:f417] ([IPv6:2601:19c:4701:878e:855:be56:282c:f417]) by resomta-ch2-06v.sys.comcast.net with ESMTPSA id fpYhfm6WZpMbFfpYifHUfk; Wed, 18 Jul 2018 16:44:12 +0000 To: pgsql-performance@postgresql.org From: George Neuner Subject: Re: Why HDD performance is better than SSD in this case Message-ID: <9c3a9ae4-25c7-c6e4-7405-a443a2a77aa9@comcast.net> Date: Wed, 18 Jul 2018 12:44:10 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CMAE-Envelope: MS4wfDenioqLVPTplSyC5FfExxZ5tNiYrsZyyk/B76SlM4+VynQcNlbj0TmQY2lu3+IHDrLSiE9EPvylX+qNxy1VZZLW/4ts47r+WzQX3OrB54zhhyJa/pDw 1BqJpSf2kDVfHOfSxLy259a+koMeGAJEgDGYCtaJOgL/yuMQhFVwIDhBiCmRhgCYxXQ0+lELfpQwQpnwsPaIYSX2GAgCAYILr79kG+MsXypDl24G6Xv7YTpX aELPTzzO09iwTiu6vNH3RL76urPwzP3QxIJoLs0ljOIYeHgn3EXXcSaWmg88kh7/ List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 18 Jul 2018 09:46:32 +0200, Fabio Pardi wrote: > RAID 0 to store production data should never be used. Never a good > idea, in my opinion. RAID 0  by itself  should never be used.  Combined with other RAID levels, it can boost performance without sacrificing reliability. https://en.wikipedia.org/wiki/Nested_RAID_levels Personally, I don't like RAID 0 + ? schemes because they use too many disks (with associated reliability issues).  The required performance usually can be achieved in other ways.  But YMMV. George