From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Question regarding performance on big files.
Date: Thu, 23 Sep 2010 17:03:39 -0500 [thread overview]
Message-ID: <4C9BCEBB.4030800@hardwarefreak.com> (raw)
In-Reply-To: <4C9B161A.1010301@opencubetech.com>
Mathieu AVILA put forth on 9/23/2010 3:55 AM:
> The small writes are amortized in the stream of data writes from the
> application, and the application is not frozen.
> (so you were right: there was a page cache issue)
Given what you've described about the streaming write behavior of your
application, I'd suggest you rewrite it and use O_DIRECT writes to
bypass the page cache completely. You may also want to look into using
the XFS realtime subvolume feature.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-09-23 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 17:04 Question regarding performance on big files Mathieu AVILA
2010-09-20 19:48 ` Stan Hoeppner
2010-09-22 10:26 ` Mathieu AVILA
2010-09-22 20:41 ` Stan Hoeppner
2010-09-23 8:55 ` Mathieu AVILA
2010-09-23 22:03 ` Stan Hoeppner [this message]
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=4C9BCEBB.4030800@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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