Personal tools
You are here: Home Personal My Blog Fedora 10 - Boot Analysis

Fedora 10 - Boot Analysis

by Harald Hoyer last modified Dec 15, 2008 20:02

A brief Fedora 10 boot analysis.

Hardware: Asus EeePC 901 with a flash disk.

Time taken from entering the encrypted root disk password until the password can be entered (after pressing return in gdm). The 10 second wait in nash is ignored here (which really annoys me and seems to be fixed in newer mkinitrd versions).

Default Live CD Installation:  39s (bootchart)

After installing readahead and running one collection boot process: 36s (bootchart)

At this point, I recognized that all processes (like newaliases), which call a fsync(), let the boot process wait until all data is written to disk. This is the same effect as the firefox sqlite fsync bug.

Mounting the root filessystem with relatime and turning off ordered data writing for the journal with

# tune2fs -o journal_data_writeback /dev/root

improved the situation (even though data might be old on the disk after a crash, but ext3 does not force the disk to empty the write cache anyway).

Turning off setroubleshoot and fixing https://bugzilla.redhat.com/show_bug.cgi?id=476023 and https://bugzilla.redhat.com/show_bug.cgi?id=476028: 32s (bootchart)

Turning off bootchart: 30s

So all in all we have nearly accomplished the 30 Second Startup Feature.

To reach the 20 Second Startup Feature, we really have to tackle setroubleshootd. Also we might start to move basic services to upstart and start them in parallel (bootchart with some services moved). Parallel booting will show no benefits with readahead and a small amount of active services, but the more services are turned on, the more you benefit with a parallel boot setup. Moving more basic modules to be compiled in the kernel also would gain some seconds. Speaking about modules, I ported Jakubs modprobe patch to the recent 3.6pre1 module-init-tools version. Though it nearly halves I/O, it would only safe us a fraction of a second here (not recognizable).

In the end, we also have to extend our view to things that happen after the user logs in (bootchart) and do an extended analysis. Work is also in progress by Gnome developer Behdad Esfahbod.

Follow the discussion on fedora-devel.

Document Actions
  • Print this
  • Hits: 007625

Re: I'm getting a penalty of 10s :-(

Posted by Harald Hoyer at Dec 15, 2008 20:04
It seems to be fixed now with mkinitrd-6.0.71-3.


Spinning Hard Disk?

Posted by Cameron at Jan 23, 2009 10:22
It would be nice if these times where done on a spinning hard disk instead of a flash hard disk. Most people have hard disk based computers and the boot time is significantly slower. With my laptop i started with a boot time of 45secs on fedora 10. I managed to get it down to 33secs.

EeePC filesystems

Posted by Anon at Feb 09, 2009 10:24
On cheap SSDs (like those currently shipped with EeePCs) it's probably wiser to stick to using ext2 lest the journal "burn" a hole in the flash: http://kernelslacker.livejournal.com/132087.html

EeePC filesystems

Posted by Harald Hoyer at Feb 09, 2009 10:42
Right.. I switched to readonly-root mode with the /home on a SD card after the tests.

Journal

Posted by mfc at Feb 10, 2009 17:29
You mean that you don't trust wear leveling on such cheap devices, do you?