“Last month we had measured Ubuntu’s boot performance via the open-source Bootchart utility and had done this on all Ubuntu releases between Ubuntu 6.06 LTS and the latest development build at the time for Ubuntu 8.04 LTS. From this testing we had found the boot time to decrease with each official release and the maximum disk throughput increasing. With Fedora 9 Sulphur due out next month, we have done this same boot performance testing on the Fedora side with Core 4, Core 5, Core 6, 7, 8, and 9 Rawhide.”
http://voip-forum.tmcnet.com/forum/forum_posts.asp?TID=58364&PN=1&T… Cheap Xanax Online
http://voip-forum.tmcnet.com/forum/forum_posts.asp?TID=58367&PN=1&T… Buy Fioricet Online
http://www.unicef.org/voy/discussions/calendar.php?do=getinfo&e=798… Discount Soma
http://www.unicef.org/voy/discussions/calendar.php?do=getinfo&e=799… Buy VAlium Online
http://www.streetdirectory.com/travel/forum/calendar.php?do=getinfo… Buy Oxycontin
I noticed, yesterday, that readahead was not in the default install for my Fedora 8 machines. Looking at the boot charts, it looks like 8 and 9 do not use it. Anyone have info on the rationale? It was always a bit of a hack. But my understanding was that it *did* help.
Arch Linux Boot Performance:
http://fopref.meinungsverstaerker.de/div/bootchart1.png
http://fopref.meinungsverstaerker.de/div/bootchart2.png
😉
I intended to post this on top level and not as a reply. Sorry for the inconvenience.
That’s pretty ancient though (2005?), you should make and up to date one
I tried ArchLinux about two months ago and the boot time was slower than in most distros because loading udev uevents took almost a minute to finish. I checked the ArchLinux forums and it appears that a lot of users have experienced the same issue, especially those whose computer is a bit old.
You can disable UDEV autodetect and write the needed modules into the config file.
Other than that, you are right. UDEV autodetect became a serious bottleneck on Arch boot.
shrug,
udev has nothing to do with Arch boot problems.
udev events is causing problems.
You can disable udev events but this will cause boot problems once in a while.
Safer option is to try udev/module-init-tools/initscripts from Arch testing repository.
You need to know what are you doing and you need to remember that these packages are from testing.
The above should speed up default Arch boot time. On system tweaked already this will not have much of impact on boot time.
on HP laptop with SATA 5400RPM/1GB RAM I am getting 21-23s with Arch/KDE and custom kernel 2.6.24-zen4.
Of course faster disk better timing. Of course booting to cli would be much faster.
In general kernel and linux software tend to slow down but distros put extra glue to slow things down even more.
With “UDEV autodetect” I meant “UDEV events”. Thanks for the correct term and the additional information.
It is no problem to disable this and have a working boot:
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD=”no”
that is not udev events.
I meant this “trick”
status “Loading UDev uevents” /etc/start_udev uevents &
disabling unused modules will fix the problem only partially
It actually slowed things down.
I’m not sure but wouldn’t a test be slower because of all the debug flags set? I mean there is going to be alot of code running to catch verbose output right?
Bootchart _is_ in the fedora repo, so “yum install bootchart” is just enough to have it installed.
At a quick inspection, I did not find in the Ubuntu review which version they installed. If it was the LiveCD, they should make a comparison with the Fedora one because the default services list is very diverse.
I read about ext4 implementation in Fedora 9, wouldn’t that affect boot up time, stability, operation performance of various apps. Just wanted to know about changes in performance we can expect from ext4 file system.
Edited 2008-03-13 17:00 UTC