From: Marcin <marcin@mejor.pl>
To: linux-bcache@vger.kernel.org
Subject: [bcachefs] time of mounting filesystem with high number of dirs
Date: Wed, 07 Sep 2016 22:09:58 +0200 [thread overview]
Message-ID: <5c0639691edb57d1b63b06effb5283d1@mejor.pl> (raw)
Hi!
I'm aware that performance doesn't have high priority, it's something
for TODO.
I created bcachefs on ~10GB partition, copied some files and next I
created huge number of directories and files. Problem is in the total
time needed for mounting filesystem.
# time mount -t bcache /dev/sde1 /mnt/test/
real 12m20.880s
user 0m0.000s
sys 1m18.270s
I looked at iostat, mounting needs to read from disk 10083588 "kB_read".
Device has size 10485760kB, so it looks that it reads almost the same
amount of data as partition size. Maybe mount time can be lower? Maybe
there can be less reads or reads could be more sequential?
Additional informations:
# time find /mnt/test/ -type d |wc -l
10564259
real 10m30.305s
user 1m6.080s
sys 3m43.770s
# time find /mnt/test/ -type f |wc -l
9145093
real 6m28.812s
user 1m3.940s
sys 3m46.210s
RAM: 1GB
CPU: core2duo - 1.86GHz
hdd: old disk SAS 15k
hdd controller: HP P400 with 512MB cache with battery
Marcin
next reply other threads:[~2016-09-07 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 20:09 Marcin [this message]
2016-09-07 21:12 ` [bcachefs] time of mounting filesystem with high number of dirs Kent Overstreet
2016-09-09 1:56 ` Kent Overstreet
2016-09-09 2:07 ` Christopher James Halse Rogers
2016-09-09 7:52 ` Marcin Mirosław
2016-09-09 9:00 ` Kent Overstreet
2016-09-12 12:59 ` Marcin
2016-09-13 2:35 ` Kent Overstreet
2016-10-05 12:51 ` Marcin Mirosław
2016-10-06 13:01 ` Kent Overstreet
2016-10-18 12:14 ` [bcachefs] time of mounting filesystem with high number of dirs aka ageing filesystem Marcin Mirosław
2016-10-18 12:45 ` Kent Overstreet
2016-10-18 12:51 ` Marcin Mirosław
2016-10-18 13:04 ` Kent Overstreet
2016-10-18 13:13 ` Marcin Mirosław
2016-10-18 13:19 ` Kent Overstreet
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=5c0639691edb57d1b63b06effb5283d1@mejor.pl \
--to=marcin@mejor.pl \
--cc=linux-bcache@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