| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Poor VMWare disk performance on XFS partition |
| From: | Andi Kleen <andi@xxxxxxxxxxxxxx> |
| Date: | 24 Mar 2008 05:02:04 +0100 |
| Cc: | "Hendrik ." <chasake@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <47E6C09E.5030601@xxxxxxxxxxx> |
| References: | <876423.51989.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <47E6C09E.5030601@xxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
Eric Sandeen <sandeen@xxxxxxxxxxx> writes: > > What does xfs_bmap and/or filefrag say, is this file indeed very > fragmented? > And is it less so on ext3? If the file is persistent then > preallocating it would probably help. Preallocating would prevent one of the main features of a sparse VM images: starting small and only growing as the virtual machine needs more storage without having to resize the virtual partitions. I remember XFS had a mmap problem a long time ago (in 2.4) which sounded similar (iirc it trickered with samba), but I thought it was long fixed. The problem back then was that page flushing on mmaps didn't get merged due to some unfortunate VM interactions and then thousands of extents got created on flushing a mmap. A lot of extents seems to make XFS slow. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] xfsqa: make 054 _require_quota, Eric Sandeen |
|---|---|
| Next by Date: | [RFC PATCH] freeze feature ver 1.0, Takashi Sato |
| Previous by Thread: | Re: Poor VMWare disk performance on XFS partition, Eric Sandeen |
| Next by Thread: | Re: Poor VMWare disk performance on XFS partition, Jan Derfinak |
| Indexes: | [Date] [Thread] [Top] [All Lists] |