|To:||Dave Chinner <david@xxxxxxxxxxxxx>|
|Subject:||Re: Improving XFS file system inode performance|
|From:||Jesse Stroik <jstroik@xxxxxxxxxxxxx>|
|Date:||Tue, 23 Nov 2010 08:49:35 -0600|
|Cc:||Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, Linux XFS <xfs@xxxxxxxxxxx>|
|References:||<4CEAE7D7.6050401@xxxxxxxxxxxxx> <20101122232528.21b78a9e@xxxxxxxxxxxxxx> <4CEAEF66.7030708@xxxxxxxxxxxxx> <20101122234419.GK13830@dastard>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:126.96.36.199) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6|
Dave,Thanks. This is precisely what I was looking for. I'll let you know how it turns out.
As this file system is likely to continue to increase in number of files at a fairly rapid rate, we're going to need a long term strategy. I suspect it may be necessary in the near future to double or quadruple the memory to 32GB or 64GB, but the uncertainty in the formula makes me nervous.
For a situation like this, it would be ideal if we could specify an inode cache size.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH v4 4/9] xfsrestore: mmap dirent names for faster lookups, Christoph Hellwig|
|Next by Date:||Re: Improving XFS file system inode performance, Dave Chinner|
|Previous by Thread:||Re: Improving XFS file system inode performance, Dave Chinner|
|Next by Thread:||Re: Improving XFS file system inode performance, Dave Chinner|
|Indexes:||[Date] [Thread] [Top] [All Lists]|