agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Bruce Momjian <bruce@momjian.us>
To: Erik Brandsberg <erik@heimdalldata.com>
Cc: Lu Dillon <ludi_1981@hotmail.com>
Cc: Iuri Sampaio <iuri.sampaio@gmail.com>
Cc: Ed Behn <ed.behn@collins.com>
Cc: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: Steve Midgley <science@misuse.org>
Cc: pgsql-sql@lists.postgresql.org <pgsql-sql@lists.postgresql.org>
Subject: Re: 回复: [External] Re: Separate volumes
Date: Fri, 10 Apr 2020 17:01:54 -0400
Message-ID: <20200410210154.GC24987@momjian.us> (raw)
In-Reply-To: <CAFcck8H1JfBE1sM98y1C+=Qfay4DayO-_gE_5hcjpX3_r4BmzQ@mail.gmail.com>
References: <CAE1kc7VfQVz0VGf4cyjaY5KYSZxrPQjPWMoEsqFTJ41-LkMOHg@mail.gmail.com>
<CAFcck8FF4T3_PL7Fa+iW5YBkA4iZ3aR2V_jka=GpV9taPph9NQ@mail.gmail.com>
<CAJexoSLSHRVOKzVGD-pDHE=KY9un7bPsxGO6fSKZVgeGsj2t6g@mail.gmail.com>
<5b60ae44-33e0-d9ea-d6e9-c6db9b4c7ef1@sqlexec.com>
<CAE1kc7W=OtwRutn+4p1ShMk+koyvv8W0JunSLiV5wMdL0OVZTw@mail.gmail.com>
<399454FC-D175-421C-AC3A-31B1082E7881@gmail.com>
<HK2PR02MB4227F498470D5CC93158DF1385C30@HK2PR02MB4227.apcprd02.prod.outlook.com>
<20200410200420.GA24987@momjian.us>
<CAFcck8H1JfBE1sM98y1C+=Qfay4DayO-_gE_5hcjpX3_r4BmzQ@mail.gmail.com>
On Fri, Apr 10, 2020 at 04:52:06PM -0400, Erik Brandsberg wrote:
> A modern filesystem can help avoid even this complexity. As an example, I am
> managing one PG setup that is self-hosted on an AWS EC2 instance, with 16TB of
> raw storage. The bulk of that storage is in ST1, or the cheapest rotating disk
> capacity available in EBS, but is using ZFS as the filesystem (with
> compression, so realistically about 35TB of raw data). The instance type is a
> Z1d.metal, which has two 900GB NVME drives, which have been divided to provide
> swap space, as well as ZFS read and write caching. This setup has largely
> offset the slow performance of the st1 disks, and kept the performance usable
> (most of the data is legacy, and rarely used). I'm a big fan of keeping the
> DB configuration simple, as it is way too easy to overlook tuning of a
> filespace for an index, causing performance problems, while if you keep it
> auto-tuning at the filesystem level, it "just works".
You are saying the cloud automatically moves data between the fast and
slow storage? I know many NAS systems do this, but I have also seen
problems when NAS systems guess wrong.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
view thread (5+ messages) latest in thread
Message-ID: <20200410210154.GC24987@momjian.us>
Permalink: ../20200410210154.GC24987@momjian.us/
Also on: postgresql.org/message-id/20200410210154.GC24987@momjian.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bruce@momjian.us, erik@heimdalldata.com, ludi_1981@hotmail.com, iuri.sampaio@gmail.com, ed.behn@collins.com, MichaelDBA@sqlexec.com, science@misuse.org, pgsql-sql@lists.postgresql.org
Subject: Re: 回复: [External] Re: Separate volumes
In-Reply-To: <20200410210154.GC24987@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox