Mailinglist Archive: opensuse-factory (422 mails)

< Previous Next >
Re: [opensuse-factory] [boottime] The effect of preload
  • From: nordi <nordi@xxxxxxxxxxxx>
  • Date: Mon, 26 Jan 2009 13:30:23 +0100
  • Message-id: <497DACDF.5000302@xxxxxxxxxxxx>
Stephan Kulow wrote:
I spent some time optimizing preload (still not done), but I wanted
to share two bootcharts for my laptop: one with preload and one
without:
Now that looks very nice! But it also shows that booting is still
largely IO-bound. CPU load remains below 50% for a big part of the time,
which means the second core is essentially idle. Would be interesting to
run this with only one active core and see how IO-bound it really is and
how much the second core is helping us.

What I find interesting is the time after 3.5 seconds. It seems that
only blogd is running, but creates neither CPU nor disk load. Since
fsck.ext3 has already finished, am I correct in the assumption that / is
already mounted? In that case there would be ~1 second between the end
of fsck and the end of blogd where not much is happening.

That should be enough to completely preload the relevant parts of /etc
and /bin, which have ~30MB on my system (not counting big stuff like
/etc/cups/yes/ppds.dat or /bin/vim-normal). Doing this should also
alleviate delays caused by reading many small files, e.g. by gconf as
mentioned by Hans Petter. But it would need a change in the initrd if
I'm not mistaken. Hmmm...

Talking about the very beginning, what is init doing between 4.5 and 6.5
seconds? Looks like it is busy waiting for IO to complete, which can
also be sped up by preloading in the initrd already.


Regards
nordi
--
Spam protection: All mail to me that does not contain the string "suse"
goes to /dev/null.

--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
References