Cheating: Not just for Microsoft anymore
Posted Oct 3, 2008 19:07 UTC (Fri) by farnz
In reply to: Cheating: Not just for Microsoft anymore
Parent article: LPC: Booting Linux in five seconds
You're missing a lot in your example timeline; let me rework it the way
it would actually happen:
- My wife is in the kitchen, and finds that she's got ingredients she'd
like to use for supper, but she'd like to use them for something different
to her normal cooking style.
- She goes into the living room, and fires up my laptop.
- She wait, knowing that as soon as it's running, she'll want to log in.
- System boots. She logs in.
- She waits, knowing that as soon as it's logged in, she'll want to run
- She clicks on the Firefox icon on her desktop.
- She waits, knowing that Firefox will come up maximised. Her mouse is
hovering over where the bookmark for the recipe site she usually uses
(when on my laptop, not hers - she has a much more complex set up on her
own machine) will be.
- Firefox starts enough that she can click on that bookmark. If the
network is not running by this point, things are broken for her, as she
can't go to the ingredient search and work out she can cook with the
contents of our fridge.
- She finds a recipe she'd like to try, and prints it - she likes to
make notes on paper of changes she makes to a recipe while cooking, so
that she can remember them easily later.
Looking at that timeline, one important thing is clear - she has
already decided to go to a particular bookmarked website
before she touches the power button. All the time taken between her
pushing the power button and the website displaying is wasted by the
computer. Thus, the only time the OS has free to waste is the time taken
by Firefox to start up after the OS has started.
Secondly, note that Firefox's start up will be slowed down if the
computer is also trying to bring up the network, start printing services
and generally do other things at the same time. It's incredibly hard to
accurately judge how much idle time you have around application start
Finally, in my experience, services are not delayed after
thinking about use cases. Instead, the delay is based on getting the bare
minimum up and running to let me log in, with functionality taking a while
to come up after that. Making the challenge "get to idle in 5 seconds"
leaves room for someone to come in later, and build on that work to get
a "get to usable in 4 seconds, idle in 6", or even a "get to usable in
under a second, but idle takes 6 seconds".
to post comments)