---Chuck Thier
>
>
> Chuck Thier
> Sent by: openstack-bounces+zhuadl=cn.ibm@lists.launchpad.net
> 2012-12-20 上午 12:33
>
>
> To
>
> David Busby ,
>
> cc
>
> "openstack@lists.launchpad.net"
>
> Subject
>
> Re: [Openstack] [sw
tack-bounces+zhuadl=cn.ibm@lists.launchpad.net
>
>2012-12-20 上午 12:33
>
>
> To
>
>
>David Busby ,
>
>
> cc
>
>
>"openstack@lists.launchpad.net"
>
>
> Subject
>
>
>Re: [Openstack] [swift] RAID Performance Issu
m@lists.launchpad
.net Subject
Re: [Openstack] [swift] RAID
Performance Issue
There are a couple of things to think about when using RAID (or more
specifically parity RAID) with swift.
The first has already been identified in that the workload for swift
is very write heavy with small random IO, which is very bad for most
parity RAID. In our testing, under heavy workloads,
Hi Zang,
As JuanFra points out there's not much sense in using Swift on top of raid
as swift handel; extending on this RAID introduces a "write penalty" (
http://theithollow.com/2012/03/21/understanding-raid-penalty/) this in turn
leads to performance issues, refer the link for write penalty's per
Hi Zang:
Basically, it makes no sense to use Swift on top of RAID because Swift just
delivers replication schema.
Regards,
JuanFra.
2012/12/19 Hua ZZ Zhang
> Hi,
>
> I have read the admin document of Swift and find there's recommendation of
> not using RAID 5 or 6 because swift performance deg
Hi,
I have read the admin document of Swift and find there's recommendation of
not using RAID 5 or 6 because swift performance degrades quickly with it.
Can anyone explain why this could happen? If the RAID is done by hardware
RAID controller, will the performance issue still exist?
Anyone can sh
7 matches
Mail list logo
