About this interactive
What you are doing: deciding, one change at a time, whether a program will run faster after it, or about as fast as before.
The lesson's rule: clock speeds have stopped climbing, mostly because of heat, so we get more done by processing more threads at once. More cores are more lanes on the freeway, a second CPU is a second freeway, and hyper-threading squeezes a couple of threads through each core. But a single-threaded program sends one thread, waits for the answer, then sends the next. Extra cores, CPUs or hyper-threading give it nothing, and it runs at the speed of the processor's clock. A multi-threaded program, or a server running many users' programs, can use the extra threads.
How to use it: ask two questions. Does the change add threads at once, or clock speed? And can this program use more than one thread? A wrong answer resets your streak and shows the right bin; land five in a row to finish.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →