Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f5nbB-00032n-Jx for pgsql-performance@arkaria.postgresql.org; Tue, 10 Apr 2018 07:21:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f5nb9-00047p-KY for pgsql-performance@arkaria.postgresql.org; Tue, 10 Apr 2018 07:21:47 +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 1f5nb9-00047Y-9Y for pgsql-performance@lists.postgresql.org; Tue, 10 Apr 2018 07:21:47 +0000 Received: from post.visena.com ([46.226.10.50]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1f5nb6-00062S-7P for pgsql-performance@lists.postgresql.org; Tue, 10 Apr 2018 07:21:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=visena.com; s=20141101.wh; h=Content-Type:MIME-Version:Subject:In-Reply-To:Message-ID:To:From:Date; bh=AHm58A+N8bS37ULVhsPdyBWk85yRBWH16bVSVlekfng=; b=oI6Sg8oxwuGUYN26SmUyHLOKy5LPmgIiuCDy8oiXNM2VLyat/fvP1Z30a2qU3DL2osTXpPg4W5Y6fGU5WhWJH3b4DSkIyIXualGLWUSDVMKr3QA0v3tqneUSmVAPh+faaAEQ2uwnuNXvayeTLbdAdH2dm5l3+e4AgZ7LGcPWERg=; Received: from [10.0.1.10] (helo=tc7-visena.wh.internal.visena.com) by post.visena.com with esmtp (Exim 4.82) (envelope-from ) id 1f5nb2-0000jJ-ER for pgsql-performance@lists.postgresql.org; Tue, 10 Apr 2018 09:21:43 +0200 Received: from localhost ([127.0.0.1] helo=tc7-visena.wh.internal.visena.com) by tc7-visena.wh.internal.visena.com with esmtp (Exim 4.86_2) (envelope-from ) id 1f5nbF-0003qh-Fx for pgsql-performance@lists.postgresql.org; Tue, 10 Apr 2018 09:21:53 +0200 Date: Tue, 10 Apr 2018 09:21:53 +0200 (CEST) From: Andreas Joseph Krogh To: pgsql-performance@lists.postgresql.org Message-ID: In-Reply-To: Subject: Sv: Latest advice on SSD? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_55_1493850074.1523344913300" X-Mailer: Visena Mail 2.1.31 X-Spam-Score: -1.0 X-Spam-Report: SpamAssasin (score=-1.0, required 5.0 ALL_TRUSTED=-1,HTML_MESSAGE=0.001) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_55_1493850074.1523344913300 Content-Type: multipart/related; boundary="----=_Part_56_1483532766.1523344913300" ------=_Part_56_1483532766.1523344913300 Content-Type: multipart/alternative; boundary="----=_Part_57_1002588719.1523344913310" ------=_Part_57_1002588719.1523344913310 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable P=C3=A5 tirsdag 10. april 2018 kl. 04:36:27, skrev Craig James >: One of our four "big iron" (spinning disks) servers went belly up today.=20 (Thanks, Postgres and pgbackrest! Easy recovery.) We're planning to move to= a=20 cloud service at the end of the year, so bad timing on this. We didn't want= to=20 buy any more hardware, but now it looks like we have to.=C2=A0 I followed the discussions about SSD drives when they were first becoming= =20 mainstream; at that time, the Intel devices were king. Can anyone recommend= =20 what's a good SSD configuration these days? I don't think we want to buy a = new=20 server with spinning disks. =C2=A0 We're replacing: =C2=A0 8 core (Intel) =C2=A0 48GB memory =C2=A0 12-drive 7200 RPM 500GB =C2=A0 =C2=A0 =C2=A0RAID1 (2 disks, OS and WAL log) =C2=A0 =C2=A0 =C2=A0RAID10 (8 disks, postgres data dir) =C2=A0 =C2=A0 =C2=A02 spares =C2=A0 Ubuntu 16.04 =C2=A0 Postgres 9.6 =C2=A0 The current system peaks at about 7000 TPS from pgbench. =C2=A0 With what arguments (also initialization)? =C2=A0 -- Andreas Joseph Krogh =C2=A0 ------=_Part_57_1002588719.1523344913310 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable
P=C3=A5 tirsdag 10. april 2018 kl. 04:36:27, skrev Craig James <cjames@emolecules.com>:
One of our four "big iron" (spinning disks) serv= ers went belly up today. (Thanks, Postgres and pgbackrest! Easy recovery.) = We're planning to move to a cloud service at the end of the year, so bad ti= ming on this. We didn't want to buy any more hardware, but now it looks lik= e we have to.
=C2=A0
I followed the discussions about SSD drives when they were first becom= ing mainstream; at that time, the Intel devices were king. Can anyone recom= mend what's a good SSD configuration these days? I don't think we want to b= uy a new server with spinning disks.
=C2=A0
We're replacing:
=C2=A0 8 core (Intel)
=C2=A0 48GB memory
=C2=A0 12-drive 7200 RPM 500GB
=C2=A0 =C2=A0 =C2=A0RAID1 (2 disks, OS and WAL log)
=C2=A0 =C2=A0 =C2=A0RAID10 (8 disks, postgres data dir)
=C2=A0 =C2=A0 =C2=A02 spares
=C2=A0 Ubuntu 16.04
=C2=A0 Postgres 9.6
=C2=A0
The current system peaks at about 7000 TPS from pgbench.
=C2=A0
With what arguments (also initialization)?
=C2=A0
">
--
Andreas Joseph Krogh
=C2=A0
------=_Part_57_1002588719.1523344913310-- ------=_Part_56_1483532766.1523344913300-- ------=_Part_55_1493850074.1523344913300--