Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bLMGY-0005CF-IY for pgsql-performance@arkaria.postgresql.org; Fri, 08 Jul 2016 03:15:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bLMGX-0000U1-VU for pgsql-performance@arkaria.postgresql.org; Fri, 08 Jul 2016 03:15:46 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bLMEs-0006of-Hd for pgsql-performance@postgresql.org; Fri, 08 Jul 2016 03:14:02 +0000 Received: from cat-porwal-prod-mail1.catalyst.net.nz ([202.78.240.226]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bLMEp-0002qA-8f for pgsql-performance@postgresql.org; Fri, 08 Jul 2016 03:14:01 +0000 Received: from localhost (localhost [127.0.0.1]) by cat-porwal-prod-mail1.catalyst.net.nz (Postfix) with ESMTP id B964880891 for ; Fri, 8 Jul 2016 15:13:55 +1200 (NZST) X-Virus-Scanned: Debian amavisd-new at cat-porwal-prod-mail1.servers.catalyst.net.nz Received: from cat-porwal-prod-mail1.catalyst.net.nz ([127.0.0.1]) by localhost (cat-porwal-prod-mail1.servers.catalyst.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktBhlUKfBs8w for ; Fri, 8 Jul 2016 15:13:54 +1200 (NZST) Received: from [192.168.1.64] (222-153-12-175.jetstream.xtra.co.nz [222.153.12.175]) (Authenticated sender: mark.kirkwood@catalyst.net.nz) by cat-porwal-prod-mail1.catalyst.net.nz (Postfix) with ESMTPSA id 9AB008089B for ; Fri, 8 Jul 2016 15:13:54 +1200 (NZST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=catalyst.net.nz; s=catalyst; t=1467947634; bh=2CnZi3In/Hv0q/qsfZIFSuZIHXWDj+8EXChjaGUouKs=; h=From:Subject:To:References:Date:In-Reply-To; b=jWSHBf1PSXodv+TS4Lg3XNdT7P2sRJeD0tBhZyzldFGjpeu5A8f8DWiUoZ+oySa5n URw2Kfl/FcDr4exprOl8GmAFeCVRu5OhFlsVpikJqmZOGS4FhEHQ3AtItJ3ZnK3I66 lWvOXNhKFBm33KKq88tS3JyZ5MSfXHwTZas2HDeo= From: Mark Kirkwood Subject: Re: Tuning guidelines for server with 256GB of RAM and SSDs? To: "pgsql-performance@postgresql.org" References: <89036cd7-e798-4e2a-a6bd-ab98641a452a@email.android.com> <577DE1C2.2010509@catalyst.net.nz> <1467900565304.12481@micron.com> Message-ID: <577F1A72.4050303@catalyst.net.nz> Date: Fri, 8 Jul 2016 15:13:54 +1200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <1467900565304.12481@micron.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 08/07/16 02:09, Wes Vaske (wvaske) wrote: > ?The Crucial drive does not have power loss protection. The Samsung drive does. > > > (The Crucial M550 has capacitors to protect data that's already been written to the device but not the entire cache. For instance, if data is read from the device during a garbage collection operation, the M550 will protect that data instead of introducing corruption of old data. This is listed as "power loss protection" on the spec sheet but it's not the level of protection that people on this list would expect from a drive) > Yes - the MX200 board (see): http://www.anandtech.com/show/9258/crucial-mx200-250gb-500gb-1tb-ssd-review looks to have the same sort of capacitors that the M550 uses, so not ideal for db or transaction logs! Cheers Mark -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance