Not really, the discussion on the original email is how to implement the underneath storage for Gluster, if use or not use RAID controllers and make the best usage of the resources. Provided performance is not mission critical but if using certain things described on the email you can get some extra (like running individual disks) is always a bonus. The main propose in that case was make better usage of the Raw spare with some level of data resilience. Fernando -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Marcus Bointon Sent: 14 June 2012 14:34 To: gluster-users at gluster.org Subject: Re: RAID options for Gluster On 14 Jun 2012, at 15:22, "Fernando Frediani (Qube)" <fernando.frediani at qubenet.net> wrote: > Well, as far as I know the amount of IOPS you can get from a RAID 5/6 is the same that you get from a single disk. The write can not be acknowledged until it is written to all the data and parity disks. It can exceed that with battery back-up on the controller. With battery back-up, writes are often faster than reads (in all of IOPS, latency and throughput), at least until you hit the cache size limit. Sustained writes will not get such good performance because of the limit you mention, but random writes can still do pretty well, YMMV. If you want to scale writes properly, you need some variant of RAID-10. I've got one server with RAID-10 across 6 SSDs, works well. Marcus -- Marcus Bointon Synchromedia Limited: Creators of http://www.smartmessages.net/ UK info at hand CRM solutions marcus at synchromedia.co.uk | http://www.synchromedia.co.uk/ _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users