From: Artem Bityutskiy <dedekind@infradead.org>
To: KeunO Park <lastnite@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: ubifs, ubiblk(formatted with vfat) and yaffs2 test.
Date: Fri, 24 Oct 2008 14:41:19 +0300 [thread overview]
Message-ID: <1224848479.4466.130.camel@sauron> (raw)
In-Reply-To: <5ed5c4730805292301m558dee30o66f5dd034d594390@mail.gmail.com>
On Fri, 2008-05-30 at 15:01 +0900, KeunO Park wrote:
> [write test]
>
> yaffs2
> write: 10.20s, 12.09s, 12.24s avg:11.51s (868KB/s)
> load avg right after copy&sync: 0.03 -> 0.11
>
> ubifs (LZO)
> write: 14.45s, 14.40s, 14.45s avg:14.43s (693KB/s)
> load avg right after copy&sync: 0.03 -> 0.53
>
> ubifs (ZLIB)
> write : 27.17s, 27.18s, 27.21s avg:27.18 (367KB/s)
> load avg right after copy&sync: 0.03 -> 0.80
>
> ubifs (No Compression)
> write: 6.69s, 10.90s, 10.98s avg:9.52s (1050KB/s)
> load avg right after copy&sync: 0.03 -> 0.43
>
> ubiblk(vfat mount)
> read: 0.46s, 0.47s, 0.46s avg: 0.463s (21.5MB/s)
> write: 12.13s, 14.95s, 12.61s avg:13.23s (755KB/s)
> load avg right after copy&sync: 0.02 -> 0.31
>
> With above result, it seems that there is some overload in ubi.
Hi,
you complained about UBIFS load average. We have added a mount
option which disabled data CRC checking. You may try it to improve
the situation. Just added this piece of documentation:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_checksumming
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-10-24 11:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 6:01 ubifs, ubiblk(formatted with vfat) and yaffs2 test KeunO Park
2008-05-30 6:33 ` Artem Bityutskiy
2008-05-30 7:15 ` KeunO Park
2008-05-30 11:34 ` Josh Boyer
2008-05-30 12:51 ` KeunO Park
2008-05-30 12:02 ` Artem Bityutskiy
2008-05-30 12:05 ` Artem Bityutskiy
2008-05-30 13:00 ` KeunO Park
2008-05-30 13:49 ` Artem Bityutskiy
2008-05-30 15:08 ` KeunO Park
2008-06-02 6:10 ` Artem Bityutskiy
2008-06-04 4:06 ` KeunO Park
2008-06-04 8:05 ` Artem Bityutskiy
2008-10-24 11:41 ` Artem Bityutskiy [this message]
[not found] <5ed5c4730805291914h187e0b0et2de31d595b52f125@mail.gmail.com>
2008-05-30 15:17 ` KeunO Park
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 5:29 References:ubifs, " Nancy
2008-06-02 6:18 ` ubifs, " Artem Bityutskiy
2008-06-02 6:47 ` Nancy
[not found] <bae050c10806012138p6167f30eu9450563efa5429ab@mail.gmail.com>
2008-06-02 5:55 ` KeunO Park
2008-06-02 6:06 ` Nancy
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=1224848479.4466.130.camel@sauron \
--to=dedekind@infradead.org \
--cc=lastnite@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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