From: Eric Sandeen <sandeen@redhat.com>
To: "Assarsson, Emil" <Emil.Assarsson@sonyericsson.com>
Cc: "michael.monnerie@is.it-management.at"
<michael.monnerie@is.it-management.at>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS memory recomendation?
Date: Fri, 17 Feb 2012 17:14:29 -0800 [thread overview]
Message-ID: <4F3EFB75.5040404@redhat.com> (raw)
In-Reply-To: <2BF070A7A2375D46BA1B6087F8D5DCB68BEA722DA4@seldmbx01.corpusers.net>
On 2/17/12 7:27 AM, Assarsson, Emil wrote:
> Thanks for the answer Dave and Michael.
>
> As you might realize, I have no knowledge if the internal works of
> XFS :-P
>
> My problem is that the file system sometimes seems to be a bit laggy
> when listing directories and so on.
This would have been a better starting point for your question. :)
> I really don't know how to deal with
> it. I guess more memory always will help but where should I put the
> limit?
How slow is slow? What kernel are you using, and what does your storage
look like? How many files are in the directory? How much memory do you
have, and what else is going on in the system at the time?
I think you'll need to quantify it a bit more.
-Eric
> Can it be a solution (ugly) to warm up the cache by making a complete
> "find" on the file system sending output to /dev/null? but then again it
> would probably be a stupid way to use precious memory for something that
> isn't used that often.
>
> --
> Emil
>
>
> fre 2012-02-17 klockan 14:05 +0100 skrev Michael Monnerie:
>> Am Freitag, 17. Februar 2012, 13:49:41 schrieb Dave Chinner:
>>> What's a "file allocation table"? XFS doesn't have one.
>>
>> I guess he means the inode/dentry cache and such.
>>
>> BTW, what's the difference of inode and dentry caches? I'd like to
>> understand the setting of
>> /proc/sys/vm/vfs_cache_pressure
>>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-18 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 11:50 XFS memory recomendation? Assarsson, Emil
2012-02-17 2:49 ` Dave Chinner
2012-02-17 13:05 ` Michael Monnerie
2012-02-17 15:27 ` Assarsson, Emil
2012-02-18 1:14 ` Eric Sandeen [this message]
2012-02-18 1:58 ` Stan Hoeppner
2012-02-18 2:17 ` Eric Sandeen
2012-02-19 13:16 ` Michael Monnerie
2012-02-19 21:00 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F3EFB75.5040404@redhat.com \
--to=sandeen@redhat.com \
--cc=Emil.Assarsson@sonyericsson.com \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox