All of lore.kernel.org
 help / color / mirror / Atom feed
From: <changfengnan@vivo.com>
To: <jaegeuk@kernel.org>, "'Chao Yu'" <chao@kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] f2fs compress performance problem
Date: Fri, 4 Jun 2021 15:31:51 +0800	[thread overview]
Message-ID: <003001d75913$aff3cc40$0fdb64c0$@vivo.com> (raw)

Hi:

I've been working on f2fs compression for a while, I'm confused on f2fs
compression performance, after a while reserch, 
I found some problem, maybe need some discuss.
I use AndroBench test performance on mobile, after enable compression, the
benchmark scores have dropped a lot.
Specifically:
1. 32M sequential read has dropped to 50% of original. Test case open file
with O_RDONLY|O_DIRECT, and set POSIX_FADV_RANDOM, the major resaon 
is disable readahed. For now,I didn't found any patch can improve this. 
2. 4K random read has dropped to 40% of original, after merge `f2fs:
compress: add compress_inode to cache compressed blocks`,
significant improvement in random read performance, up to 90% of original,
maybe more.
3. 32M sequential overwrite has dropped to 10% of original, after merge
`f2fs: compress: remove unneeded read when rewrite whole cluster`
up to 30% of original.
4. 4K random read has dropped to 1% of original, yes only 1% of original, I
found  open file with O_WRONLY|O_DSYNC|O_DIRECT is  an important reason, 
every time sync a compress inode need do checkpoint, after I remove
checkpoint on compress inode, up to 10% of original. And I think major
reason of this
is we need read whole cluster and rewrite it ,but I did't think of any
method to improve this.

I want to know is there any idea can help to improve this.
And I want to know do we have goal for the performance of compression, is it
possible to achieve the original performance?

Thanks.



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2021-06-04  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  7:31 changfengnan [this message]
2021-07-01 17:06 ` [f2fs-dev] f2fs compress performance problem Jaegeuk Kim
2021-07-02  2:40   ` Fengnan Chang
2021-07-02  6:24     ` Jaegeuk Kim
2021-07-06 13:12       ` Fengnan Chang

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='003001d75913$aff3cc40$0fdb64c0$@vivo.com' \
    --to=changfengnan@vivo.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.