From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Subject: ext3_group_sparse slow?
Date: Tue, 11 Jan 2005 15:48:43 +0100 [thread overview]
Message-ID: <20050111144843.GG15061@atrey.karlin.mff.cuni.cz> (raw)
Hello!
I've been profiling dbench load on ext3 on my laptop and it looks as
follows:
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
samples % symbol name
100485 23.2633 __copy_to_user_ll
54497 12.6166 __copy_from_user_ll
34702 8.0339 acpi_processor_idle
15107 3.4974 link_path_walk
8229 1.9051 __d_lookup
6540 1.5141 ext3_group_sparse
6490 1.5025 __might_sleep
4972 1.1511 sysenter_past_esp
3981 0.9216 kmem_cache_alloc
3797 0.8790 ext3_readdir
3617 0.8374 find_get_page
3615 0.8369 ext3_get_group_desc
3589 0.8309 ext3_do_update_inode
...
What caught my eye is that ext3_group_sparse() and also
ext3_get_group_desc() take so much time. OK, it's only 1.51 and 0.84 percent
of the processor time and it is clearly pretty much dominated by the IO
but anyway I think we need not spend so much processor time by such
trivial operations :) Do you think it would be worth improving?
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next reply other threads:[~2005-01-11 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 14:48 Jan Kara [this message]
2005-01-11 18:37 ` ext3_group_sparse slow? Andreas Dilger
2005-01-12 14:18 ` Jan Kara
2005-01-12 18:23 ` Andreas Dilger
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=20050111144843.GG15061@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@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).