From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | robert(at)webtent(dot)com |
Cc: | "Bill Moran" <wmoran(at)potentialtech(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: autovacuum |
Date: | 2007-09-20 21:33:25 |
Message-ID: | dcc563d10709201433o5db3fd30m6e460565bcb82fe6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/20/07, Robert Fitzpatrick <lists(at)webtent(dot)net> wrote:
> On Thu, 2007-09-20 at 16:38 -0400, Bill Moran wrote:
> > In response to Robert Fitzpatrick <lists(at)webtent(dot)net>:
> > Why does everyone leave of the IO subsystem? It's almost as if many
> > people don't realize that disks exist ...
> >
> > With 2G of RAM, and a DB that's about 3G, then there's at least a G of
> > database data _not_ in memory at any time. As a result, disk speed is
> > important, and _could_ be part of your problem. You're not using RAID
> > 5 are you?
>
> Yes, using RAID 5, not good? RAID 5 with hot fix total of 4 drives. All
> SATA 80GB drives giving me little under 300GB to work with.
RAID5 optimizes for space, not performance or reliability. It gets
faster but less reliable as it gets bigger. If you can afford the
space RAID-10 is generally preferred.
Note however that it is far more important for most general purpose
servers to have a RAID controller that is both fast by nature (i.e.
not $50.00) and has battery backed cache with write thru turned on.
RAID5 on a fast controller with battery backed cache is ok. But I've
seen software RAID-10 outrun it for certain loads...
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-20 22:00:52 | Re: PG levels vs. syslog levels |
Previous Message | Jerry Sievers | 2007-09-20 21:32:35 | Adding domain type with CHECK constraints slow on large table |