Thanks for those options. My machines tend to be self-healing rather frequently. Doing a gluster volume heal VMARRAY info the file list cycles through most of my high IOPS machines Also what's the best way to apply those options with out bricking the running VM's? I just made a rough stab and took the cluster down. ----- Original Message ----- From: "Vijay Bellur" <vbellur@xxxxxxxxxx> To: "Josh Boon" <gluster@xxxxxxxxxxxx>, "Nick Majeran" <nmajeran@xxxxxxxxx> Cc: "Gluster-users@xxxxxxxxxxx List" <gluster-users@xxxxxxxxxxx> Sent: Saturday, March 22, 2014 1:36:09 PM Subject: Re: Optimizing Gluster (gfapi) for high IOPS On 03/21/2014 09:50 PM, Josh Boon wrote: > Hardware RAID 5 on SSD's using LVM formatted with XFS default options > mounted with noatime > > Also I don't a lot of history for this current troubled machine but the > sysctl additions don't appear to have made a significant difference Performance tunables in [1] are normally recommended for qemu - libgfapi. The last two options are related to quorum and the remaining tunables are related to performance. It might be worth a check to see if these options help provide better performance. Do you happen to know if self-healing was in progress when the machines stall? -Vijay [1] https://github.com/gluster/glusterfs/blob/master/extras/group-virt.example _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
