| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS Preallocate using ALLOCSP |
| From: | Smit Shah <getsmit@xxxxxxxxx> |
| Date: | Tue, 16 Jun 2009 14:38:12 -0700 |
| Cc: | Felix Blyakher <felixb@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dDGfsdIiTHsQq+ptWfll78CzcQKrrLnyG+kMBCXSzXc=; b=GKDPH8f+4NyGgP5SYqadPiRwwKCTHfSJfAJwGK/1joDxptNrKjRLR9lMF7qMSmBCQX Ut5Pbk2Ra3HPmv34hWyESzIO+rPevCD8rnDMYLUJXoewUYZCaTvsVneD1mS+SivTQ7Ag iYd7UtNYDDLa0VbxMyj62qO+AODV65n+kCE7w= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xuzaRKtuZQeyNLgXb8fmGmHD131NRrw88+0VVOxo0glOlNpr9QgmYrmHH3HXMrTlnU 7GpR4uJwLmAClTF3oP/goB4MJzU59irYYuqE47N+VJZBXTPjWhhLKCMTmTv6mUgLT/N4 gSmsVgY3tGfv78yQOBI/d0SqnZ6AN7364oboQ= |
| In-reply-to: | <4A37D737.70004@xxxxxxxxxxx> |
| References: | <24042506.post@xxxxxxxxxxxxxxx> <4A3712BF.7030101@xxxxxxxxxxx> <8770d98c0906152344p185533a9rc144a5667d13d2de@xxxxxxxxxxxxxx> <4A37B744.9030301@xxxxxxxxxxx> <0B774481-16A5-42FC-89C3-91096E59E861@xxxxxxx> <8770d98c0906161028j1cc5cbadl49d30092fddf3dbe@xxxxxxxxxxxxxx> <4A37D737.70004@xxxxxxxxxxx> |
In the vmware sparse disk, the chunks are allocated of the size of 64k, which kindof leads to fragmentation. Hence the sequential read throughput suffers. So thought it might be a good idea to preallocate some amount memory say 50Meg when it asks for allocating the chunk thus helps in reducing fragmentation and improves the throughput. On linux i do preallocation using fallocate. I have vmware workstation running Windows Vista and host is RHEL 5.3 with the guest having 1GB of memory and host having 2 Gig. And i have separate dedicated SATA disk on which i perform the tests. For testing, I create a new sparse vdisk and run a IOmeter sequential write on it. For ext4 i tend to get say around 5-6 Mbps of improvement in write throughput sometimes but it never goes down. But for XFS i always see atleast 8-10 Mbps of downfall. -Smit On 6/16/09, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: > Smit Shah wrote: >> On 6/16/09, Felix Blyakher <felixb@xxxxxxx> wrote: >>> On Jun 16, 2009, at 10:16 AM, Eric Sandeen wrote: > > >>>> Maybe I should ask what the end goal is here. :) >>>> >> Just to see if preallocation using fallocate helps reducing the >> fragmentation and increases the throughput. I guess it wll help >> reduce the fragmentation but the write performance is going to suffer. > > Depends on the IO you do, I think. I'd be curious to know exactly how > you're running preallocation & iometer so I could give it a shot, to see > why xfs seems to be doing worse than ext4. > > Thanks, > -Eric > |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS Preallocate using ALLOCSP, Felix Blyakher |
|---|---|
| Next by Date: | Re: XFS Preallocate using ALLOCSP, Smit Shah |
| Previous by Thread: | Re: XFS Preallocate using ALLOCSP, Eric Sandeen |
| Next by Thread: | Re: XFS Preallocate using ALLOCSP, Michael Monnerie |
| Indexes: | [Date] [Thread] [Top] [All Lists] |