| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Fragmentation Issue We Are Having |
| From: | Richard Scobie <richard@xxxxxxxxxxx> |
| Date: | Fri, 20 Apr 2012 07:54:50 +1200 |
| Cc: | b.candler@xxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 |
Brian Candler wrote: -------------------------- Ah, that's new to me. So with inode32 and sysctl fs.xfs.rotorstep=255 you can get roughly the same locality benefit for sequentially-written filesas inode64? (Aside: if you have two processes writing files to two different directories, will they end up mixing their files in the same AG? That could hurt performance at readback time if reading them sequentially) ----------------------------- The "filestreams" mount option may be of use here, see: http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide//tmp/en-US/html/ch06s16.html and page 17 of: http://oss.sgi.com/projects/xfs/training/xfs_slides_06_allocators.pdf Regards, Richard |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: task blocked for more than 120 seconds, Josef 'Jeff' Sipek |
|---|---|
| Next by Date: | Re: [PATCH 2/5] xfs: reduce ilock hold times in xfs_file_aio_write_checks, Ben Myers |
| Previous by Thread: | Re: Fragmentation Issue We Are Having, Dave Chinner |
| Next by Thread: | [PATCH] fs/xfs/xfs_dinode.h: fix comments of xfs_dinode_t., Chen Baozi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |