PREDICT · EXPERIMENT · EXPLAIN

Can you predict what happens?

Choose one of six learning routes. Predict the result, follow the state changes, check a prerequisite when needed, then try different conditions. No installation is needed.

EXPERIMENT 01 · ABOUT 10 MIN

Predict cache eviction

Trace A → B → A → C → B in a two-entry LRU cache.

  1. Save your prediction before running
  2. Follow the state, one step at a time
  3. Check the reason, revisit a prerequisite, then change conditions
Start or resume →

EXPERIMENT 02 · ABOUT 10 MIN

Translate an address with a page table

Translate the 16-bit virtual address 0x1234 using 256-byte pages.

  1. Save your prediction before running
  2. Follow the state, one step at a time
  3. Check the reason, revisit a prerequisite, then change conditions
Start or resume →

EXPERIMENT 03 · ABOUT 10 MIN

Trace stacks and queues

Predict removed values and remaining entries from put/take operations.

  1. Save your prediction before running
  2. Follow the state, one step at a time
  3. Check the reason, revisit a prerequisite, then change conditions
Start or resume →

EXPERIMENT 04 · ABOUT 10 MIN

Count operations as inputs change

Count one specified body operation in a loop.

  1. Save your prediction before running
  2. Follow the state, one step at a time
  3. Check the reason, revisit a prerequisite, then change conditions
Start or resume →

EXPERIMENT 05 · ABOUT 10 MIN

Predict box widths and positions

Compute box positions and widths in an explicitly simplified vertical layout model.

  1. Save your prediction before running
  2. Follow the state, one step at a time
  3. Check the reason, revisit a prerequisite, then change conditions
Start or resume →

EXPERIMENT 06 · ABOUT 10 MIN

Predict asynchronous execution order

Trace synchronous work, microtasks and tasks under explicit scheduling rules.

  1. Save your prediction before running
  2. Follow the state, one step at a time
  3. Check the reason, revisit a prerequisite, then change conditions
Start or resume →

Your first answer and your observations stay separate

A completed experiment is a record of what you tried. It does not, by itself, mean that you have mastered the concept. Your prediction and the reason question are recorded separately.

Progress is saved in this browser. Clearing browser data removes it. These experiments use explicitly defined learning models; they are not measurements of a real CPU or operating system.