From: Wim Coekaerts <wim.coekaerts@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] flush
Date: Wed Jul 7 03:34:46 2004 [thread overview]
Message-ID: <20040707083442.GA9197@ca-server1.us.oracle.com> (raw)
for those that are going to be awake now ;-)
sys_close() -> filp_close() -> ocfs_fops() -> ocfs_flush() -> fsync_buffers_list()
that happens on close. flush causes a sync to disk
so
untar of a full tree took 6:15 min
then took out the ocfs_sync_inode() from ocfs_file_release()
then lowered heartbeat to 1 per second nad commit interval now at 5
seconds
then went down to bout 4:30 minutes
then noticed the flush during untar, so I got rid of ocfs_flush() as a
test
went down to bout 2 minutes, however things are inconsistent
so it's not tha simple .but that's a huge part of the remaining
bottlenecks when comparing stuff to ext3
next reply other threads:[~2004-07-07 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 3:34 Wim Coekaerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 4:55 [Ocfs2-devel] flush Ling, Xiaofeng
2004-07-07 11:03 ` Wim Coekaerts
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=20040707083442.GA9197@ca-server1.us.oracle.com \
--to=wim.coekaerts@oracle.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.