From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
Curt Wohlgemuth <curtw@google.com>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: [PATCH 0/5 v2] Improve sync(2) handling
Date: Wed, 27 Jul 2011 00:38:01 +0200 [thread overview]
Message-ID: <1311719886-1130-1-git-send-email-jack@suse.cz> (raw)
Hello,
this is a second iteration of my series improving handling of sync syscall.
Since previous submission I have incorporated Christoph's suggestions and
also measured some numbers.
Unpatched kernel Patched kernel
time for (( i = 0; i < 100; i++ )); do sync; done
1.130400 +- 0.027369 1.073200 +- 0.040848
create 20000 4k files and sync (XFS)
155.995600 +- 1.879084 155.942200 +- 1.843881
create 20000 4k files and sync (ext3)
154.597200 +- 1.556965 153.109800 +- 1.339094
run while true; do time sync; sleep 5; done while creating 32 MB files in
parallel (xfs)
6.466727 +- 0.710062 5.716000 +- 0.574406
run while true; do time sync; sleep 5; done while creating 32 MB files in
parallel (ext3)
15.969909 +- 3.732143 7.662909 +- 2.268830
We see that when we are not writing in parallel to sync (the last test) there
are no big improvements. When writing while running sync, ext3 got a nice boost
from saving one pass over inodes. XFS got improved only slightly.
Comments are welcome.
Honza
next reply other threads:[~2011-07-26 22:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 22:38 Jan Kara [this message]
2011-07-26 22:38 ` [PATCH 1/5] vfs: Make sync(1) writeout also block device inodes Jan Kara
2011-07-27 9:44 ` Christoph Hellwig
2011-07-28 20:13 ` Jan Kara
2011-07-26 22:38 ` [PATCH 2/5] vfs: Move noop_backing_dev_info check from sync into writeback Jan Kara
2011-07-27 9:44 ` Christoph Hellwig
2011-07-26 22:38 ` [PATCH 3/5] quota: Split dquot_quota_sync() to writeback and cache flushing part Jan Kara
2011-07-27 8:26 ` Steven Whitehouse
2011-07-27 9:45 ` Christoph Hellwig
2011-07-26 22:38 ` [PATCH 4/5] quota: Move quota syncing to ->sync_fs method Jan Kara
2011-07-27 8:32 ` Steven Whitehouse
2011-07-27 9:46 ` Christoph Hellwig
2011-07-27 13:44 ` Dave Kleikamp
2011-07-26 22:38 ` [PATCH 5/5] vfs: Avoid unnecessary WB_SYNC_NONE writeback during sync(1) Jan Kara
2011-07-27 9:52 ` Christoph Hellwig
2011-07-28 17:42 ` Jan Kara
2011-07-28 20:37 ` Christoph Hellwig
2011-07-28 21:20 ` Curt Wohlgemuth
2011-07-29 11:09 ` Christoph Hellwig
2011-09-28 15:00 ` [PATCH 0/5 v2] Improve sync(2) handling Christoph Hellwig
2011-10-06 22:20 ` Jan Kara
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=1311719886-1130-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=curtw@google.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).