From: Vlad Apostolov <vapo@sgi.com>
To: Vlad Apostolov <vapo@sgi.com>
Cc: Michael Nishimoto <miken@agami.com>, David Chinner <dgc@sgi.com>,
Michael Nishimoto <miken@stanfordalumni.org>,
xfs@oss.sgi.com
Subject: Re: Reducing memory requirements for high extent xfs files
Date: Wed, 06 Jun 2007 09:17:24 +1000 [thread overview]
Message-ID: <4665EF04.5020803@sgi.com> (raw)
In-Reply-To: <4665ED89.4090202@sgi.com>
Vlad Apostolov wrote:
> Michael Nishimoto wrote:
>>
>>
>> David Chinner wrote:
>>> On Wed, May 30, 2007 at 09:49:38AM -0700, Michael Nishimoto wrote:
>>> > Hello,
>>> >
>>> > Has anyone done any work or had thoughts on changes required
>>> > to reduce the total memory footprint of high extent xfs files?
>>>
>>> We changed the way we do memory allocation to avoid needing
>>> large contiguous chunks of memory a bit over a year ago;
>>> that solved the main OOM problem we were getting reported
>>> with highly fragmented files.
>>>
>>> > Obviously, it is important to reduce fragmentation as files
>>> > are generated and to regularly defrag files, but both of these
>>> > alternatives are not complete solutions.
>>> >
>>> > To reduce memory consumption, xfs could bring in extents
>>> > from disk as needed (or just before needed) and could free
>>> > up mappings when certain extent ranges have not been recently
>>> > accessed. A solution should become more aggressive about
>>> > reclaiming extent mapping memory as free memory becomes limited.
>>>
>>> Yes, it could, but that's a pretty major overhaul of the extent
>>> interface which currently assumes everywhere that the entire
>>> extent tree is in core.
>>>
>>> Can you describe the problem you are seeing that leads you to
>>> ask this question? What's the problem you need to solve?
>>>
>>> Cheers,
>>>
>>> Dave.
>>> --
>>> Dave Chinner
>>> Principal Engineer
>>> SGI Australian Software Group
>>
>> I realize that this work won't be trivial which is why I asked if anyone
>> has thought about all relevant issues.
>>
>> When using NFS over XFS, slowly growing files (can be ascii log files)
>> tend to fragment quite a bit. One system had several hundred files
>> which required more than one page to store the extents. Quite a few
>> files had extent counts greater than 10k, and one file had 120k extents.
>> Besides the memory consumption, latency to return the first byte of the
>> file can get noticeable.
>>
>> Michael
>>
> Hi Michael,
>
> You could use XFS_XFLAG_EXTSIZE and XFS_XFLAG_RTINHERIT flags to
> set extent hint size, which would reduce the file fragmentation in
> this scenario.
> Please check xfcntl man page for more details.
>
> Regards,
> Vlad
I meant XFS_XFLAG_EXTSZINHERIT not XFS_XFLAG_RTINHERIT. This one
should be set on a parent directory.
Regards,
Vlad
next prev parent reply other threads:[~2007-06-05 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 16:49 Reducing memory requirements for high extent xfs files Michael Nishimoto
2007-05-30 22:55 ` David Chinner
2007-06-05 22:23 ` Michael Nishimoto
2007-06-05 23:11 ` Vlad Apostolov
2007-06-05 23:17 ` Vlad Apostolov [this message]
2007-06-06 1:36 ` David Chinner
2007-06-06 2:00 ` Vlad Apostolov
2007-06-06 2:05 ` Vlad Apostolov
2007-06-06 17:18 ` Michael Nishimoto
2007-06-06 23:47 ` David Chinner
2007-06-22 23:58 ` Michael Nishimoto
2007-06-25 2:47 ` David Chinner
2007-06-26 1:26 ` Nathan Scott
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=4665EF04.5020803@sgi.com \
--to=vapo@sgi.com \
--cc=dgc@sgi.com \
--cc=miken@agami.com \
--cc=miken@stanfordalumni.org \
--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