From: John Reiser <jreiser-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: building initramfs is slow
Date: Thu, 18 Aug 2011 16:09:19 -0700 [thread overview]
Message-ID: <4E4D9B9F.9030001@bitwagon.com> (raw)
In-Reply-To: <CALAkbJOkMTQdkmhBBvqHk3oKRzMHvXcp1MxasMrMpCbTP3+0eg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 08/18/2011 11:25 AM, Harald Hoyer wrote:
> Try dracut version 013. It's already faster.
Yes, there is some improvement, but I still seek a *factor* of 3 to 4
overall before cpio+gzip. All the slow coding persists.
$ time /abs/path/to/dracut-013/dracut --local --force test2.img
### [fixed-width font, please] contrast to dracut-011
real 59s +3s
user 26s +6s
sys 29s -2s
26.0MB output image + 11.1MB
69.0MB unzipped + 28.0MB
1947 files listed by cpio +328 files
483 .ko kernel modules +116 modules
## Note the results have gotten larger (time, bytes, files, modules).
## The input (and configuration) has evolved, too.
$ strace -o strace.out -f -e trace=execve /abs/path/to/dracut-013/dracut --local --force test2.img
11349 SIGCHLD -1169 processes !yea!
7544 execve -1373 execve !yea!
3805 fork-and-no-exec + 214 shell builtins that get a process
2686 execve("/bin/egrep" -1117 good, but should be at most a few dozen
1587 execve("/bin/cp" + 244
491 execve("/sbin/modinfo" + 116
468 execve("/bin/chmod" + 109
458 execve("/bin/rm"
455 execve("/sbin/modprobe"
320 execve("/bin/readlink"
318 execve("/bin/mkdir"
285 execve("/lib64/ld-linux..." -573 !yea!
166 execve("/usr/bin/ldd" -594 !yea!
119 execve("/bin/cat"
88 execve("/bin/ln"
44 execve("/bin/grep"
17 execve("/bin/find"
--
next prev parent reply other threads:[~2011-08-18 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 18:18 building initramfs is slow John Reiser
[not found] ` <CALAkbJOkMTQdkmhBBvqHk3oKRzMHvXcp1MxasMrMpCbTP3+0eg@mail.gmail.com>
[not found] ` <CALAkbJOkMTQdkmhBBvqHk3oKRzMHvXcp1MxasMrMpCbTP3+0eg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-18 23:09 ` John Reiser [this message]
2011-08-19 4:53 ` WANG Cong
2011-08-19 6:47 ` Harald Hoyer
[not found] ` <4E4E0707.4060504-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-19 7:04 ` Américo Wang
[not found] ` <CAM_iQpUr2mVRM+PFeYkefzx9xEAOJKhZh+wpaXgKg6bj+1dozQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-19 7:07 ` Harald Hoyer
[not found] ` <4E4E0B95.6040909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-19 7:32 ` Dan Horák
2011-08-19 18:27 ` John Reiser
[not found] ` <4E4D5779.6090209-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
2011-08-19 7:03 ` Harald Hoyer
2011-08-19 8:24 ` Harald Hoyer
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=4E4D9B9F.9030001@bitwagon.com \
--to=jreiser-po6cbstgb2zwk0htik3j/w@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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