From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id 0FB067F7D for ; Sat, 30 Mar 2013 14:12:41 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay2.corp.sgi.com (Postfix) with ESMTP id D659C30404E for ; Sat, 30 Mar 2013 12:12:37 -0700 (PDT) Received: from greer.hardwarefreak.com (mo-65-41-216-221.sta.embarqhsd.net [65.41.216.221]) by cuda.sgi.com with ESMTP id fvcLD4MfwnnwcNUh for ; Sat, 30 Mar 2013 12:12:37 -0700 (PDT) Message-ID: <51573924.2020304@hardwarefreak.com> Date: Sat, 30 Mar 2013 14:12:36 -0500 From: Stan Hoeppner MIME-Version: 1.0 Subject: Re: Help with XFS in VMs on VMFS References: <51549F09.1090109@hardwarefreak.com> <20130328214550.GA3771@pirx.askja.de> <5154E6AC.9020402@hardwarefreak.com> <20130329202735.GX22182@sgi.com> In-Reply-To: <20130329202735.GX22182@sgi.com> Reply-To: stan@hardwarefreak.com List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Ben Myers Cc: Jan Perci , xfs@oss.sgi.com On 3/29/2013 3:27 PM, Ben Myers wrote: > 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 Is this really a good idea given that XFS sits atop a virtual disk which consists of multiple concatenated 2TB sparse files sitting on the VMFS filesystem, which, IIRC, has a 1MB sector size? Thus can one rely on XFS being able to properly align to the physical RAID stripe, even if the math is done 'properly' (if that's even possible here)? In a complex stack like this I'd recommend defaults across the board. Misalignment hurts performance far more than proper alignment increases it. No alignment is agnostic, 4KB IOs only, so you neither gain nor lose. > 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. -- Stan _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs