Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dixdc-0004fk-T3 for pgsql-performance@arkaria.postgresql.org; Sat, 19 Aug 2017 06:53:41 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dixdb-0006u6-Q0 for pgsql-performance@arkaria.postgresql.org; Sat, 19 Aug 2017 06:53:39 +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 1dixbp-0003r8-UK for pgsql-performance@postgresql.org; Sat, 19 Aug 2017 06:51:50 +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 1dixbh-0003b7-6O for pgsql-performance@postgresql.org; Sat, 19 Aug 2017 06:51:47 +0000 Received: from localhost (localhost [127.0.0.1]) by cat-porwal-prod-mail1.catalyst.net.nz (Postfix) with ESMTP id BECB680867; Sat, 19 Aug 2017 18:51:36 +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 BiTqIkVG3qoR; Sat, 19 Aug 2017 18:51:34 +1200 (NZST) Received: from [IPv6:2406:e001:a50:1:3997:77ba:9d91:623f] (unknown [IPv6:2406:e001:a50:1:3997:77ba:9d91:623f]) (Authenticated sender: mark.kirkwood@catalyst.net.nz) by cat-porwal-prod-mail1.catalyst.net.nz (Postfix) with ESMTPSA id 3F4BA807C1; Sat, 19 Aug 2017 18:51:34 +1200 (NZST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=catalyst.net.nz; s=catalyst; t=1503125494; bh=knK59oL9if3OhYN0exHgCAynM1AT9aVBX1JzYNPQ5AQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=SpFaU79Lhkq9F9Af5kOl8cHWfB7ZGljlpK54FrIjj3gZEO+5MGoF7d5KxMnY9I8mg 99fXbC9Hw3J66ZeAvn7ZNO/uNE/KZnVDDDoqHvpOcd1XtG+syRXjxjgDB20Aq1+Xww wx9MfUwcP3/q5iPsBCmFgRTVhLv/QCbqQ9tUYZPY= Subject: Re: Very poor read performance, query independent To: Charles Nadeau Cc: "pgsql-performa." References: From: Mark Kirkwood Message-ID: Date: Sat, 19 Aug 2017 18:51:34 +1200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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 Nice! Pleased that the general idea worked well for you! I'm also relieved that you did not follow my recommendation exactly - I'm been trialling a Samsung 960 Evo (256GB) and Intel 600p (256GB) and I've stumbled across the serious disadvantages of (consumer) M.2 drives using TLC NAND - terrible sustained write performance! While these guys can happily do ~ 2GB/s reads, their write performance is only 'burst capable'. They have small SLC NAND 'write caches' that do ~1GB/s for a *limited time* (10-20s) and after that you get ~ 200 MB/s! Ouch - my old Crucial 550 can do 350 MB/s sustained writes (so two of them in RAID0 are doing 700 MB/s for hours). Bigger capacity drives can do better - but overall I'm not that impressed with the current trend of using TLC NAND. regards Mark On 21/07/17 00:50, Charles Nadeau wrote: > Mark, > > I received yesterday a second server having 16 drives bays. Just for a > quick trial, I used 2 old 60GB SSD (a Kingston V300 and a ADATA SP900) > to build a RAID0. To my surprise, my very pecky RAID controller (HP > P410i) recognised them without a fuss (although as SATAII drives at > 3Gb/s. A quick fio benchmark gives me 22000 random 4k read IOPS, more > than my 5 146GB 10k SAS disks in RAID0). I moved my most frequently > used index to this array and will try to do some benchmarks. > Knowing that SSDs based on SandForce-2281 controller are recognised by > my server, I may buy a pair of bigger/newer ones to put my tables on. > > Thanks! > > Charles > > On Sat, Jul 15, 2017 at 1:57 AM, Mark Kirkwood > > > wrote: > > Thinking about this a bit more - if somewhat more blazing > performance is needed, then this could be achieved via losing the > RAID card and spinning disks altogether and buying 1 of the NVME > or SATA solid state products: e.g > > - Samsung 960 Pro or Evo 2 TB (approx 1 or 2 GB/s seq scan speeds > and 200K IOPS) > > - Intel S3610 or similar 1.2 TB (500 MB/s seq scan and 30K IOPS) > > > The Samsung needs an M.2 port on the mobo (but most should have > 'em - and if not PCIe X4 adapter cards are quite cheap). The Intel > is a bit more expensive compared to the Samsung, and is slower but > has a longer lifetime. However for your workload the Sammy is > probably fine. > > regards > > Mark > > On 15/07/17 11:09, Mark Kirkwood wrote: > > Ah yes - that seems more sensible (but still slower than I > would expect for 5 disks RAID 0). > > > > > -- > Sent via pgsql-performance mailing list > (pgsql-performance@postgresql.org > ) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > > > > > > -- > Charles Nadeau Ph.D. > http://charlesnadeau.blogspot.com/ -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance