From: Yan Zheng <yanzheng@21cn.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Random write regression
Date: Tue, 21 Jul 2009 15:04:04 +0800 [thread overview]
Message-ID: <3d0408630907210004g34a49196xb235aa2f6a1f0f1b@mail.gmail.com> (raw)
In-Reply-To: <4A646D0E.1060006@austin.ibm.com>
2009/7/20 Steven Pratt <slpratt@austin.ibm.com>:
> Finally got around to going through latest data. =A0Seems like we los=
t all the
> random write performance gains. =A0Creates are better, but total regr=
ession on
> the random workload. =A0Sequential reads seem to have dropped as well=
=2E
>
> Results are uploading now.
> =A0http://btrfs.boxacle.net/repository/raid/history/History.html
>
> These are for RAID only as single disk system still having issues com=
pleting
> btrfs runs. =A0Also, missing oprofile duw to oprofile causing an NMI =
and
> killing the system.
>
> Chris, this was built on 7/6, but I see no new changes sine 7/2/.
> Steve
>
>
The output of ffsb in the latest 128 threads random odirect write bench=
mark was
=2E...
checking existing fs: /mnt/ffsb1
fs setup took 6 secs
Syncing()...2 sec
=2E...
The corresponding output on 30 June was
=2E...
creating new fileset /mnt/ffsb1
fs setup took 847 secs
Syncing()...1 sec
=2E...
It seems the filesystem used in the latest benchmark wasn't freshly cre=
ated.
Yan, Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-21 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 13:11 Random write regression Steven Pratt
2009-07-20 13:34 ` Chris Mason
2009-07-20 14:47 ` Steven Pratt
2009-07-21 7:04 ` Yan Zheng [this message]
2009-07-21 14:48 ` Steven Pratt
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=3d0408630907210004g34a49196xb235aa2f6a1f0f1b@mail.gmail.com \
--to=yanzheng@21cn.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.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