linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Amr H. El-Sharnoby" <amr.el.sharnoby@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: du and find is much slower on btrfs than ext4
Date: Mon, 23 Aug 2010 16:03:01 +0200	[thread overview]
Message-ID: <AANLkTin+O_evkoK577eyivnt=Xo1ffMEzX8aamcRw1ep@mail.gmail.com> (raw)

Hello,
I've noticed that running "du -sch" on a btrfs takes much longer that
it on ext4 filesystem have the exact same copy of data ...
Also, running "find -type f" for example is much slower on btrfs that ext4 ...

I could reproduce this on;
1- a single 64GB Intel X-25E SSD
2- and on a 6 x 1TB SATA II disks on RAID-0

Notes:
1- Both filesystems have been recently populated with the same copy of data
2- I'm using -o compress for btrfs

Thanks

-- Amr H. El-Sharnoby --

             reply	other threads:[~2010-08-23 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 14:03 Amr H. El-Sharnoby [this message]
     [not found] <AANLkTintDx=zT7wARJ0UzchamAjfkZ3fcDyR5+-zYCes@mail.gmail.com>
2010-08-23 14:02 ` du and find is much slower on btrfs than ext4 Amr El-Sharnoby

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='AANLkTin+O_evkoK577eyivnt=Xo1ffMEzX8aamcRw1ep@mail.gmail.com' \
    --to=amr.el.sharnoby@gmail.com \
    --cc=linux-btrfs@vger.kernel.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).