logo       

Re: RAID5 crash and burn: msg#00288

linux.raid

Subject: Re: RAID5 crash and burn

> If you are seriously considering the performance implications of RAID1
> vs RAID5 for swap, you are already done for performance wise.

I disagree. the whole point of Linux's approach to swap is that
it's fairly cheap to write a page to swap. whether you ever need
it again depends on how overcommitted you are. this is assuming that
the kernel successfully chooses not-likley-to-be-reused pages to
write to swap, and that your swap partitions are reasonably fast
to write to. this approach works very well, excepting heuristic problems
in certain kernel versions.

in other words, reading from swap is permitted to be expensive,
since any disk read is always assumed to be slow. but writing to
swap really should be fairly cheap, and this is a premise of the
kernel's swap policies.

I would not use raid5 swap for this reason; raid1 is not insane,
since you don't need *that* much swap space, so the 50% overhead
is not crippling. (don't even think about things like raid 10
for swap - the kernel already has zero-overhead swap striping.)

regards, mark hahn.

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise