From: | Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com> |
---|---|
To: | Gregg Jaskiewicz <gryzman(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: table spaces |
Date: | 2013-03-09 18:08:21 |
Message-ID: | CAKwGa_-Kz908VAhWTrWrbNwCD=M-fdBT9dWHA9mig1f4ns_iFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Gregg
yes, keep the indexes on a separate channel. Much depends on how the
data is mapped and accessed, sometimes even distributing the data
itself onto different spaces may do good.
If you use a lot of logging (say you feed a massive pgFouine
activity), you would want to have that on yet another separate
channel, too.
There is no universal bullet for this, iostat will eventually tell you
whether your load distribution is good enough, or not.
Cheers
Bèrto
On 9 March 2013 17:51, Gregg Jaskiewicz <gryzman(at)gmail(dot)com> wrote:
> Performance related question.
> With Linux (centos 6.3+), 64bit, ext4 in mind, how would you guys go about
> distributing write load across disks.
>
> Lets say I have quite few disks, and I can partition them the way I want, in
> mirror configuration (to get some hardware failure resilience). Should I
> separate tables from indexes onto separate raids ?
>
> I know WAL has to go on a separate disk, for added performance.
>
> I'm looking for your experiences, and most importantly how do you go about
> deciding which way is best. I.e. which combinations make sense to try out
> first, short of all permutations :-)
>
> Thanks.
>
>
>
> --
> GJ
--
==============================
If Pac-Man had affected us as kids, we'd all be running around in a
darkened room munching pills and listening to repetitive music.
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Jungwirth | 2013-03-09 19:54:24 | Splitting Postgres into Separate Clusters? |
Previous Message | Gregg Jaskiewicz | 2013-03-09 17:51:10 | table spaces |