| To: | "Jeffrey W. Baker" <jwbaker@xxxxxxx> |
|---|---|
| Subject: | Re: ZFS, XFS, and EXT4 compared |
| From: | Nathan Scott <nscott@xxxxxxxxxx> |
| Date: | Thu, 30 Aug 2007 17:07:46 +1000 |
| Cc: | zfs-discuss@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx |
| In-reply-to: | <1188454611.23311.13.camel@xxxxxxxxxxxxxxxxxxxx> |
| Organization: | Aconex |
| References: | <1188454611.23311.13.camel@xxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | nscott@xxxxxxxxxx |
| Sender: | xfs-bounce@xxxxxxxxxxx |
On Wed, 2007-08-29 at 23:16 -0700, Jeffrey W. Baker wrote: > ... xfs has great > sequential transfer but really bad metadata ops, like 3 minutes to tar > up the kernel. Perhaps this is due to the write barrier support - would be interesting to try a run with the "-o nobarrier" mount option to XFS. With external logs, write barriers are automatically disabled, which may explain: "Oddly XFS has better sequential reads when using an external journal, which makes little sense." To improve metadata performance, you have many options with XFS (which ones are useful depends on the type of metadata workload) - you can try a v2 format log, and mount with "-o logbsize=256k", try increasing the directory block size (e.g. mkfs.xfs -nsize=16k, etc), and also the log size (mkfs.xfs -lsize=XXXXXXb). Have fun! cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [zfs-discuss] ZFS, XFS, and EXT4 compared, Cyril Plisko |
|---|---|
| Next by Date: | Re: [zfs-discuss] ZFS, XFS, and EXT4 compared, mike |
| Previous by Thread: | Re: [zfs-discuss] ZFS, XFS, and EXT4 compared, Cyril Plisko |
| Next by Thread: | Re: ZFS, XFS, and EXT4 compared, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |