Originally posted by russofris
View Post
Announcement
Collapse
No announcement yet.
A Two-Second Boot Time With systemd
Collapse
X
-
-
Originally posted by johnc View PostThere are a lot of people who still don't use suspend-to-ram, suprisingly.
I boot maybe once every 10-30 days for a variety of reasons, and the boot time is short enough now that it never concerns me.
Comment
-
@russofris
Well compared to coreboot uefi is slow. But every new system has got uefi (well done w8) and the old way would be activating the csm for bios compat at the end and run old mbr grub code or use uefi to boot efi grub. So when you skip that and directly load the kernel - without initrd as that would require efi shell access (maybe patching efibootmgr to support options would be enough) you definitely save a few seconds. It also depends a bit on the uefi vendor, Insyde (which is used by ASUS) is a bit slow i would say. You definitely gain more speed than switching from sysvinit (makefile mode) to systemd.
Comment
-
Originally posted by curaga View PostHuh, I look out of place here not using suspend even though it works. Just no point in it when boot is 5s and procudes a much cleaner environment.
I'm personally happy with suspend (on the laptop it works reliably on) and mainly do a reboot if my batteries run out.
Comment
-
Originally posted by curaga View PostHuh, I look out of place here not using suspend even though it works. Just no point in it when boot is 5s and procudes a much cleaner environment.
Rumor is it does use <5 watts of power in suspend mode, though my UPS always reports zero, even with two computers in suspend. But it could be that the UPS is not capable of accurately reporting energy usage that low.
Comment
-
Originally posted by johnc View PostTrue... but I tend to like it because I don't have to close down my open applications every night, which is especially useful when I'm doing something like, say, development and have 4 million billion trillion windows open.
In instances where my work PC shuts down overnight, I am often confused and slow in the morning. Step 1 is trying to restore my browser session so I can figure out WTF I was working on last night. Step 2 is to start my e-mail client and letting the 400 overnight messages from APOC/DVCI regions sync (20-30 mins). Step 3 is to find my in-progress work.
It takes 1 hour and two coffees from the time I turn on my PC until I am able to do any actual work. It's gotten so bad that I had to implement a VM on my iMac specifically for on-call work (10 minute response SLA). It's sad that the windows VM on my iMac sleeps properly, but my Win 7 T400 does not.
F
Comment
-
Originally posted by curaga View PostHuh, I look out of place here not using suspend even though it works. Just no point in it when boot is 5s and procudes a much cleaner environment.
And for a lot of us, having to start with a 'clean environment' is a total mega epic PITA punishment because it takes forever to get everything back in working order and in the right place. I don't even care how long it takes to wake up from suspend or hibernate as long as I get my shit back the way I left it.
Besides, the boot time pissing contest days will hopefully be over soon, with the trend going towards always-on or deep-sleep stuff like what win8+ultrabooks are aiming for.
Comment
Comment