+1 ms while the chain has work, matching cronAlarmDelayMs() and the fill chain
in src/site-do.js: a fresh invocation is a fresh CPU budget, and re-arming
immediately also keeps the object resident, which is what stops a hibernation
discarding the interpreter between two update hooks.
A cold beat waits longer -- there is nothing this chain can do to boot
an interpreter inside 10 ms, so it backs off and lets traffic or the keep-warm
alarm do it.
When the next alarm should fire.
+1 ms while the chain has work, matching
cronAlarmDelayMs()and the fill chain in src/site-do.js: a fresh invocation is a fresh CPU budget, and re-arming immediately also keeps the object resident, which is what stops a hibernation discarding the interpreter between two update hooks.A cold beat waits longer -- there is nothing this chain can do to boot an interpreter inside 10 ms, so it backs off and lets traffic or the keep-warm alarm do it.