From: Chao Yu <yuchao0@huawei.com>
To: lampahome <pahome.chen@mirlab.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Can I know if now is gc-ing or checkpointing?
Date: Mon, 6 Jul 2020 15:46:20 +0800 [thread overview]
Message-ID: <a80be8b3-75d1-33c8-a4da-b4c336ae53be@huawei.com> (raw)
In-Reply-To: <CAB3eZfsjaNxMK+0HqYNAQQgksgGZNOO7QAXoT_Lgqr1+mPss3w@mail.gmail.com>
On 2020/7/6 15:34, lampahome wrote:
> Chao Yu <yuchao0@huawei.com> 於 2020年7月6日 週一 下午3:29寫道：
>>
>> On 2020/7/6 15:10, lampahome wrote:
>>> I tried to test performance with f2fs and create many fio to test it.
>>>
>>> I found when fio reach a number(e.g. 25 fio), the performance degrade
>>> not in proportional with small number
>>>
>>> EX:
>>> 5 fio: bandwidth 300MB/s
>>> 10 fio: bandwidth 150MB/s
>>> 25 fio: bandwidth 30MB/s
>>
>> What's your buffer size for each flush?
Could you share the whole command?
>>
> Each fio submit blocksize=4k, direct=0, 1GB file. So buffer size is 4k?
I meant how many data fio will write before triggering fsync?
I doubt that __should_serialize_io() may serialize all fio threads if your
buffer size is larger than size of one section (2MB by default)
>
> When grep GC and CP in f2fs status, it shows did GC and CP some times.
> But my disk has 128GB and each fio only write 1GB file.
> Why does the behavior trigger GC and CP?
Can you share result of status before and after test?
There is BGGC and FGGC, BGGC runs periodically, FGGC runs when there is
almost no free segments; CP trigger condition is complicated, commonly,
via syncfs.
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-07-06 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 7:10 [f2fs-dev] Can I know if now is gc-ing or checkpointing? lampahome
2020-07-06 7:29 ` Chao Yu
2020-07-06 7:34 ` lampahome
2020-07-06 7:46 ` Chao Yu [this message]
2020-07-06 8:11 ` lampahome
2020-07-06 8:51 ` Chao Yu
2020-07-06 8:58 ` lampahome
2020-07-06 10:27 ` Chao Yu
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=a80be8b3-75d1-33c8-a4da-b4c336ae53be@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=pahome.chen@mirlab.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;
as well as URLs for NNTP newsgroup(s).