| To: | Jan Perci <jperci@xxxxxxxxx> |
|---|---|
| Subject: | Re: Help with XFS in VMs on VMFS |
| From: | Ben Myers <bpm@xxxxxxx> |
| Date: | Fri, 29 Mar 2013 15:27:35 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAJoqCq_afu4d++fgkGGMDC55pcz62V3qyai906ihQ2d=eiyhhQ@xxxxxxxxxxxxxx> |
| References: | <CAJoqCq9WhFi8yZnTjh_dJmOte4TWpKg3qsQLpVsZ45M8XoWiaA@xxxxxxxxxxxxxx> <51549F09.1090109@xxxxxxxxxxxxxxxxx> <20130328214550.GA3771@xxxxxxxxxxxxx> <5154E6AC.9020402@xxxxxxxxxxxxxxxxx> <CAJoqCq_afu4d++fgkGGMDC55pcz62V3qyai906ihQ2d=eiyhhQ@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
Hi Jan, On Thu, Mar 28, 2013 at 11:30:01PM -0400, Jan Perci wrote: > Back to XFS, in this context, is there any benefit in tuning some > parameters to get better performance, or will it all just be overshadowed > by poor performance of the VMDKs that tuning isn't worthwhile? At least get your stripe unit and width correct. http://xfs.org/index.php/XFS_FAQ#Q:_How_to_calculate_the_correct_sunit.2Cswidth_values_for_optimal_performance Beyond that I suggest you stick with the defaults unless you have a specific need. e.g. heavy usage of extended attributes might prompt you to use a larger inode size to keep them inline. Regards, Ben |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_fsr, sunit, and swidth, Dave Hall |
|---|---|
| Next by Date: | 1 an de produits Kinder à remporter !, Kinder |
| Previous by Thread: | Re: Help with XFS in VMs on VMFS, Jan Perci |
| Next by Thread: | Re: Help with XFS in VMs on VMFS, Stan Hoeppner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |