From: lampahome <pahome.chen@mirlab.org>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Increase blocksize won't help performance?
Date: Fri, 3 Jul 2020 15:21:39 +0800 [thread overview]
Message-ID: <CAB3eZftAfxfJwA2fBC5A1wMsyvGchf1XY4ffZ4TweGO1SS_puQ@mail.gmail.com> (raw)
I am a new to F2FS and want to test a basic benchmark of F2FS.
My environment is to create multiple fio threads(5 and 10) with
blocksize 4K and 2MB to know how the performance is.
And the results shows 4K is always better than 2MB.
I originally thought 2MB is faster because it fits the segment size.
So 4K always be fast is because F2FS process each IO of 4K? Even if
blocksize sets to 2MB, it will divide it into multiple 4K units to
process?
thanks
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2020-07-03 7:29 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=CAB3eZftAfxfJwA2fBC5A1wMsyvGchf1XY4ffZ4TweGO1SS_puQ@mail.gmail.com \
--to=pahome.chen@mirlab.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).