[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Bootup speed for F8



Here is my bootchart from initng [1]
with the note that NetworkManager doesn't want to start and sound is
out of the question as well.

Those first 8 seconds are exactly the same in initd [2] as they are in
initng. With initd it isn't much of an issue because it's slow already
and ust doesn't mather much. with initng it's nearly HALF of the boot
time!! now it's gonna something that would be nice to get fixed.

About looking in scripts in initrd.. how do you do that? is there a
guide for it somewhere? or is this [3] still good for it?

[1] http://img252.imageshack.us/img252/2538/bootchartpx1.png
[2] http://img530.imageshack.us/img530/6483/bootchartsw0.png
[3] http://www.mail-archive.com/unattended-info lists sourceforge net/msg04445.html

2007/12/1, David Zeuthen <david fubar dk>:
>
> On Fri, 2007-11-30 at 21:50 -0800, Jesse Barnes wrote:
> > On Friday, November 30, 2007 6:06 pm Dimi Paun wrote:
> > > On Fri, 2007-11-30 at 11:18 -0500, Bill Nottingham wrote:
> > > > 1) bootchart weirdness (as it's from when bootchart starts)
> > > > 2) hotplug issues with a driver in the initrd not initializing
> > > > right
> > >
> > > Well, maybe, but I think it's a common problem:
> > >     http://lattica.com/pub/bootchart-20071130-f8.png
> > >
> > > In my case, that initial time is close to 11s! And mind
> > > you, it's no bootchard weirdness, I've always noticed it.
> >
> > Yeah, I'm seeing the same thing, ~10s on one machine and ~15s on
> > another.  I briefly looked at the nash scripts and hotplug code in the
> > initrd.  It looks like we spend a lot of time waiting for the kernel to
> > generate hotplug events and settle down the devices... I'm not sure how
> > much of it could reasonably be trimmed, maybe comparing to a non-initrd
> > config would make sense?  I think this is pjones' stuff, so there are
> > probably good reasons for the way things are.
>
> In the perfect world (and on 99% of the other distros), the initramfs
> can exit to real user space as soon as the root device is mounted.
>
> I know that on Fedora (at least in the past) we play some really ugly
> tricks to make sure that the kernel names (e.g. sda, sdb etc.) for the
> devices are in a specific order (scsi_wait_scan.ko etc.). Seems
> literally like a waste of time; better fix the rest of the OS not to
> rely on things like kernel names.
>
> Then again, I haven't looked at this for some time... It would be
> interesting to compare to other distros like SUSE, Debian and Ubuntu to
> see how much slower or faster we are.
>
>        David
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]