Re: [SPAM] Re: autovacuum disk IO

From: Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: [SPAM] Re: autovacuum disk IO
Date: 2016-03-02 18:54:07
Message-ID: 56D736CF.2010908@evolu-s.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-performance

Il 02/03/2016 19:40, Alvaro Herrera ha scritto:
> 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.
>
Definitely. I my new server (as I've been taught here :-) ) I'm going to
put stats in a ramdisk and pg_xlog in another partition.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message drum.lucas@gmail.com 2016-03-03 00:56:12 pg_dump limit 1000 rows
Previous Message Alvaro Herrera 2016-03-02 18:40:26 Re: [SPAM] Re: autovacuum disk IO

Browse pgsql-performance by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2016-03-04 17:28:02 Re: [ADMIN] autovacuum disk IO
Previous Message Alvaro Herrera 2016-03-02 18:40:26 Re: [SPAM] Re: autovacuum disk IO