VOGONS

Common searches


First post, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

https://blogs.msdn.microsoft.com/oldnewthing/ … 502-00/?p=93395

I remember some magazine article about Windows 8, and it talked about how fast Windows 8 started up compared to Windows 7. The w […]
Show full quote

I remember some magazine article about Windows 8, and it talked about how fast Windows 8 started up compared to Windows 7. The way they measured it was by putting a shortcut to Notepad in the Startup group, then booting the computer, and timing how long before the Notepad window opened.

I laughed at this metric because I control when startup groups start up. As in me, personally.

The Explorer startup sequence has a number of phases, carefully arranged to get visible things ready first, and less visible things ready later. And one of the lowest priority items is the Startup group.

In fact, even after everything is finished initializing, there is a bonus extra delay before the Startup group gets processed. We’ve found that one of the big frustrations people have with Windows is that after signing in, they can’t use the computer because all of the Startup programs are thrashing the computer. Launching all the programs in the Startup group and similar auto-start locations (like the Run key) means that you have a dozen programs all trying to load themselves off the disk, which thrashes the computer so hard that the user can’t even open the Start menu.

There have been a variety of approaches taken to mitigate the impact of auto-start programs. One trick was to run auto-start programs in a box that keeps them at low CPU and disk priority for 60 seconds. In Windows 8, one new trick was to delay launching the next program until the previous one has settled down, where “settled down” means “stopped consuming a lot of CPU and disk I/O bandwidth.” Another trick was simply to wait longer before starting the auto-start programs in the first place.

Measuring how long it takes for Notepad to open is in large part simply a way of extracting the parameter I passed to the Sleep function.

I could have made Windows boot faster or slower according to their metrics by simply tweaking how long I slept before firing up the auto-start programs.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 2 of 4, by Errius

User metadata
Rank l33t
Rank
l33t

I always assume the computer will be unusable for the first ~5 minutes after boot and go do something else while it settles down.

“Your mission is to attack and destroy the Apple Computer manufacturing plant. You are allotted 35 bombs and 60 lasers."

Reply 3 of 4, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

I must admit it would be nice if this sort of thing was plainly documented somewhere rather than having to be explicitly discussed on Mr. Chen's blog. But then again, even if something is documented somewhere, there's no guarantee people will ever look at it.

Reply 4 of 4, by mrau

User metadata
Rank Oldbie
Rank
Oldbie

on windows its a sad norm already, getting even slower and less responsive just because visible things are loaded first and then pushed out from memory partially because the background tasks "have to" run -.- ; i was more frustrated when it begun happening on linux after switching to btrfs 😒 im just not used to seeing the login prompt and not being able to type in my credentials T.T this is all an elaborate plan of bill's, i know it!