From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
Cc: | Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Need to tune for Heavy Write |
Date: | 2011-08-04 08:46:02 |
Message-ID: | CAOR=d=3kjpFdLS5xeVL9JnFXynY+BANtr+k7B0gZSRwOS5gKGA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Aug 4, 2011 at 2:34 AM, Willy-Bas Loos <willybas(at)gmail(dot)com> wrote:
> On Thu, Aug 4, 2011 at 6:56 AM, Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)com> wrote:
>> After this I change my pg_xlog directory to a separate directory other than
>> data directory by symlinking.
>>(...)
>> Please let me know if I missing any other important configuration.
>
> Moving the pg_xlog to a different directory only helps when that
> directory is on a different harddisk (or whatever I/O device).
Not entirely true. By simply being on a different mounted file
system this moves the fsync calls on the pg_xlog directories off of
the same file system as the main data store. Previous testing has
shown improvements in performance from just using a different file
system.
That said, the only real solution to a heavy write load is a heavy
duty IO subsystem, with lots of drives and battery backed cache.
From | Date | Subject | |
---|---|---|---|
Next Message | Dusan Misic | 2011-08-04 09:03:13 | Re: Need to tune for Heavy Write |
Previous Message | Dusan Misic | 2011-08-04 08:43:25 | Re: Need to tune for Heavy Write |