From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFD] ocfs2: poor performance on append write/punch hole
Date: Tue, 28 Jan 2014 17:53:05 +0800 [thread overview]
Message-ID: <52E77E01.9010902@huawei.com> (raw)
In ocfs2_file_aio_write, it will fall back to buffered IO when cannot
complete direct IO request, e.g. append write and punch hole. And mostly
it should firstly do space allocation and this will make much more
journal to flush.
From test, we found the above two cases performs almost 70% lower than
normal case(allocate space first and overwrite). Furthermore, it spends
more than 90% time on jbd2_journal_force_commit during aio write.
So if anyone have an idea on how to tune the performance on these two cases?
reply other threads:[~2014-01-28 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52E77E01.9010902@huawei.com \
--to=joseph.qi@huawei.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.