From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Joseph Hammerman <joe.hammerman@datadoghq.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Postgres on L2ARC
Date: Mon, 23 Jan 2023 20:39:45 -0700
Message-ID: <729B87B1-DE36-4876-9488-8F4C19DD3EF8@elevated-dev.com> (raw)
In-Reply-To: <CAHs7QM-SHvb8kwHXCat4WEP0RP7BzQv9aF-HUDP2qbKx2jB-pw@mail.gmail.com>
References: <CAHs7QM-SHvb8kwHXCat4WEP0RP7BzQv9aF-HUDP2qbKx2jB-pw@mail.gmail.com>
> On Jan 23, 2023, at 6:18 PM, Joseph Hammerman <joe.hammerman@datadoghq.com> wrote:
>
> Has anyone built a Postgers architecture using L2ARC, and potentially TABLESPACES to mount the ZFS pools (dedicated one per table). I am imagining the ZFS pools would be backed by EBS volumes.
Yes. It worked fine, but much smaller and less busy than what you're probably planning for. Originally, Ubuntu 16 & older ZFS, PG data was on mirrorz SSD, with other SSD partitions for L2ARC & ZIL. Later, at a major update, I did some benchmarking, and got rid of the SSD dedicated to ZFS. Then the SSD became entirely ZIL & L2ARC, and PG shared L2ARC with other data.
So, to be clear, in this case the reason for having PG use L2ARC with spinning rust behind it was that the PG did not need dedicated SSD for performance...
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-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, joe.hammerman@datadoghq.com, pgsql-admin@lists.postgresql.org
Subject: Re: Postgres on L2ARC
In-Reply-To: <729B87B1-DE36-4876-9488-8F4C19DD3EF8@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox