Re: [SPAM] Re: autovacuum disk IO

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: [SPAM] Re: autovacuum disk IO
Date: 2016-03-02 18:40:26
Message-ID: 20160302184026.GA436128@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-performance

Scott Marlowe wrote:
> On Wed, Mar 2, 2016 at 9:11 AM, Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Moreno Andreo 2016-03-02 18:54:07 Re: [SPAM] Re: autovacuum disk IO
Previous Message Scott Marlowe 2016-03-02 16:21:02 Re: [SPAM] Re: autovacuum disk IO

Browse pgsql-performance by date

  From Date Subject
Next Message Moreno Andreo 2016-03-02 18:54:07 Re: [SPAM] Re: autovacuum disk IO
Previous Message Scott Marlowe 2016-03-02 16:21:02 Re: [SPAM] Re: autovacuum disk IO