Chromium OS Fast Boot
Chromium OS Fast Boot
Google Chrome OS is an open source operating system for people who spend most of their time on the web built around the core tenets of speed, simplicity and security. http://www.chromium.org
Content
0 ->
0.57 -> Hi, I'm Martin Bligh,
working on system
2.52 -> software for Chrome OS.
4.44 -> In this video, we're going to
discuss one of the cool goals
6.61 -> of Chrome OS, which is speed.
10.04 -> That means end-to-end
measurements,
11.88 -> redesign and tuning.
13.54 -> But we're going to start by
looking at one specific
15.17 -> example, which is boot speed.
18.78 -> Our goal is to get the user
from pressing the power
20.98 -> button to the web as
quickly as possible.
23.95 -> Let's start by looking at what
you have to go through on
25.87 -> a traditional operating
system to get to email.
29.06 -> The user presses the power
button and the computer
30.7 -> firmware starts.
32.69 -> The firmware searches for
components that could be inside
34.62 -> the computer and also looks for
ones that could be plugged in
36.83 -> externally and initializes
them one at a time.
40.33 -> Then they display a pretty
splash screen, just in case you
42.83 -> forgot who made your laptop.
45.47 -> After the firmware finishes,
it loads and starts
47.62 -> the bootloader.
48.63 -> The bootloader loads
and starts the kernel.
51.65 -> The kernel searches for
components again and
54.21 -> initializes them again.
57.15 -> Then they put up another
splash screen, just in case
59.35 -> you forgot who sold you
the operating system.
62.02 -> A complex set of services and
applications gets started.
65.93 -> Now the user gets to log
into the operating system.
69.36 -> It then fires up all
the applications in
70.96 -> your start folder.
72.43 -> Over the years, these
applications have grown
74.11 -> very large and cumbersome.
76 -> Often this includes parts of
applications you don't even
78.01 -> need yet, just so they look
faster when you do go to start.
82.06 -> Start antivirus software
to protect yourself
83.99 -> against malware.
85.61 -> Then the user gets to
click on a browser icon.
89.63 -> Now you have to log in again
to cloud services like Gmail.
94.01 -> How does that change
with Chrome OS?
96.44 -> Our goal is to boot from
power to the web in
99.32 -> just a few seconds.
101.28 -> We also set a budget of
resuming from suspend
103.5 -> in under a second.
105.27 -> So we set out to do some
serious spring cleaning and
107.12 -> simplification, starting by
measuring and analyzing every
110.58 -> millisecond of bootup time.
112.54 -> Let's look at some of the
things we're changing.
115.24 -> This is an appliance-sold
device so we already know
117.32 -> what's on the machine.
118.55 -> You don't have to go
searching for it.
120.8 -> We're not going to issue a
command and then sleep for 20
122.85 -> seconds to wait and see if you
have a floppy disk
124.88 -> drive connected.
126.94 -> Initializing hardware is slow.
128.78 -> By moving it from the firmware
to the kernel, we can start
131.68 -> multiple devices in
[? parallel. ?]
133.86 -> For example, we can keep
streaming data from the
135.86 -> disk while we wait for the
video display to start.
139.44 -> Let's get rid of those
splash screens.
140.94 -> They just waste time.
143.48 -> We don't need a bootloader.
144.59 -> We can just jump
straight to the kernel.
148.15 -> We're simplifying complex
layers of legacy software.
150.58 -> The browser is the focal
point of the system now.
153.97 -> This is a native web device
so you don't have to
155.95 -> log in twice either.
158.7 -> We're also using solid-state
storage devices, like in your
161.26 -> camera or your phone, not hard
disk drives, a technology
165.06 -> invented over 50 years ago.
167.37 -> That means there's
no moving parts.
169.32 -> We don't have to wait for a
mechanical [? head-on ?]
171.44 -> to move from side to side
before we can get your data.
174.03 -> When you close the lid, the
netbook would go to sleep.
176.77 -> When you open it, it'll
wake up in under a second.
179.93 -> Simple.
180.9 -> So if you're a systems
engineer, take a look through
183 -> this and let us know,
what else can we cut out?
185.18 ->
196.16 -> Can we get it in four seconds?
197.46 -> Three?
198.76 -> Go to chromium.org
and learn more.
201.19 ->
Source: https://www.youtube.com/watch?v=mTFfl7AjNfI