Going from 2.3 to 3.5 seconds is a dramatic change, not a small one.
It's a 50% increase, and it's even worse if it proportional in the sense that a sense booting in 23 seconds with systemd boots with 3.5 seconds with upstart.
Anyway, if they were using an SSD or ramdisk, those timings are still horrible, since boot ought to be instantaneous.
Posted Nov 27, 2012 17:38 UTC (Tue) by man_ls (subscriber, #15091)
[Link]
Proportions are meaningless since both start systems are doing a number of discrete tasks, not a continuous sequence. When Upstart went from 35 to 23 seconds it was a huge advantage; now that systemd uses just one less second, it is immaterial in practice.
Anyway, if they were using an SSD or ramdisk, those timings are still horrible, since boot ought to be instantaneous.
Really? Let us do some quick math: SATA III achieves 600 MB/sec. If your userspace is 1 GB (not unheard of), then it will take about two seconds just to load all that information from disk into memory. This is besides any hardware initialization tasks, computations and so on. I think that 2.5 seconds in real life is an impressive achievement, even for a modest userspace. It will never be "instantaneous" even with the fastest SSD money can buy, at least until SATA VII or so (just joking, at that point userspace will probably be about 8 GB). But for my particular needs we are well beyond the point of diminishing returns.
Remarks about the benchmark
Posted Nov 27, 2012 20:30 UTC (Tue) by cyanit (guest, #86671)
[Link]
Due to existence of live CDs, the userspace needed to boot is clearly much smaller than 1 GB.
Also, you could cheat by having GRUB2 display the login screen and handle password input itself, loading the Linux kernel in background while the password is typed.