From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Moreno Andreo <moreno.andreo@evolu-s.it>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: [SPAM] Re: autovacuum disk IO
Date: Wed, 2 Mar 2016 15:40:26 -0300
Message-ID: <20160302184026.GA436128@alvherre.pgsql> (raw)
In-Reply-To: <CAOR=d=0vOZGfBbYB4iR8YwLnN+MKB58kPXG45f=18yMzr5UD2w@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Scott Marlowe wrote:
> On Wed, Mar 2, 2016 at 9:11 AM, Moreno Andreo <moreno.andreo@evolu-s.it> wrote:
> > ... or maybe add some more RAM to have more disk caching (if you're on
> > *nix).... this worked for me in the past... even if IMHO it's more a
> > temporary "patch" while upgrading (if it can't be done in a hurry) than a
> > real solution...
>
> Oh yeah, definitely worth looking at. But RAM can't speed up writes,
> just reads, so it's very workload dependent. If you're IO subsystem is
> maxing out on writes, faster drives / IO. If it's maxing out on reads,
> more memory. But if your dataset is much bigger than memory (say 64GB
> RAM and a 1TB data store) then more RAM isn't going to be the answer.
In the particular case of autovacuum, it may be helpful to create a
"ramdisk" and put the stats temp file in it.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-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: alvherre@2ndquadrant.com, scott.marlowe@gmail.com, moreno.andreo@evolu-s.it, pgsql-performance@postgresql.org
Subject: Re: [SPAM] Re: autovacuum disk IO
In-Reply-To: <20160302184026.GA436128@alvherre.pgsql>
* 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