When Computing Time is Time Lost
summary
Two theoretical models appear: one designs fast timers that decide whether a heuristic will exceed a deadline by testing the actual input, the other treats computation time as lost execution time and optimizes the planning/execution split. Concrete tools: random-pair inversion estimator gives a constant‑time, nearly complete timer for bubble sort; Fibonacci‑type inputs certify many steps for Euclid’s GCD; scheduling uses a tau parameter for DP cost and a DP+greedy mix that outperforms full DP when planning eats real time.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:43Real time decision making
- 2:52Turning Heuristics into Good Algorithms
- 5:35For correctness ... Program Checkers
- 6:20Timers: Similar idea for running time
- 8:49Simple Observations
- 10:48Probabilistic Timers
- 13:21Generalizing...
- 15:49Another example
- 18:34Other problems with timers
- 20:49Scheduling
- 22:46Dynamic Programming for Standard Version
- 26:11A Better Alternative
