linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: guorke <guorke@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: F2FS performance drop than ext4
Date: Mon, 11 Nov 2013 09:35:36 +0900	[thread overview]
Message-ID: <1384130136.14041.82.camel@kjgkr> (raw)
In-Reply-To: <CACby0kmwCBK=UcvHSiNrzSBice-6tkagmqr3UwRVO1LfQObufg@mail.gmail.com>

Hi,

As I checked the commit, I suspect that you turned on
CONFIG_DEBUG_MUTEXES in your .config.
Could you test without this kind of debugging configs?
Because f2fs uses many mutexes which results in high SW overhead.
Thanks,

2013-11-09 (토), 10:31 +0800, guorke:
> Dear all,
> 
> I test f2fs performace via androbench with lot of f2fs commits.  And i
> found that, before commit
> bfe35965ecdc6038314d03456b94d9ba451c289d(2013/05/28), the
> sequential/random io and sqlite operation performance is better than
> ext4.  After this commit, the io performance drop too much,  even test
> it with the latest commit.   And test result shows it slower than
> ext4(~15%), like sequential read,sqlite insert/update/delete
> operation,but random write still faster than ext4(~200%).    
> F2fs freeze all io operations when do a checkpoint,  but ext4 no this
> design,  the checkpoint freeze operation block others metat data
> update.   in android phone, most application use sqlite , which it
> caused lot of fsync/fdatasync. And this sync operation would cause lot
> of checkpoint operation , than it caused database perfomance drop.
> There's some optimization about writecheckpoint from fs_lock, to
> semphone. but it is useless.
> 
> any suggestion about it ?
> 
> Ps, 
> 1. androbench is  a tool which use to monitor android phone io
> performance,  it use fsync/fdatasync to simulate random io and sqlite
> database operation.
> 2. F2fs use default mount option, ext4 use
> rw,noatime,noauto_da_alloc,commit=1,data=ordered.
> 
> 
> 
> thanks
> 
> gourke
> 
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most 
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

-- 
Jaegeuk Kim
Samsung



------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2013-11-11  0:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  2:31 F2FS performance drop than ext4 guorke
2013-11-11  0:35 ` Jaegeuk Kim [this message]

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=1384130136.14041.82.camel@kjgkr \
    --to=jaegeuk.kim@samsung.com \
    --cc=guorke@gmail.com \
    --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).