Motion 09
Yielding work
Each run scores the same number of 52 week plans, 364 days each with 7 and 42 day load averages, sized on the first run for about 300 ms of work on the machine it runs on.
From the Engineering page on ramtt.com
- Blocking runs them as one task, so no frame is drawn and a key typed meanwhile waits until the end.
- Yielding gives the main thread back every 5 ms with scheduler.yield, so frames keep coming and keys are handled at once; the frames drawn in between add to the total, and the table shows how much.
- The longest task comes from long animation frames, then long tasks, then the longest gap between frames.