Does ONE beat and hands back whether the caller should re-arm.
Two beats per unit -- claim then run -- and the docblock at the top of this
file explains why that is not one: a crash marker written in the same event that
enters PHP dies with the event it was supposed to outlive, because DO SQLite
commits its implicit transaction at the end of each event.
maxBeats above 1 is a PAID-PLAN setting. On free it must stay 1, for two
reasons: nothing in this file bounds a single unit's CPU (there is no clock to
bound it with), and batching collapses the per-unit crash granularity that the
claim beat buys.
The beat's own shape is UpdbBeat, declared at the top of this file.
Does ONE beat and hands back whether the caller should re-arm.
Two beats per unit --
claimthenrun-- and the docblock at the top of this file explains why that is not one: a crash marker written in the same event that enters PHP dies with the event it was supposed to outlive, because DO SQLite commits its implicit transaction at the end of each event.maxBeatsabove 1 is a PAID-PLAN setting. On free it must stay 1, for two reasons: nothing in this file bounds a single unit's CPU (there is no clock to bound it with), and batching collapses the per-unit crash granularity that the claim beat buys.The beat's own shape is
UpdbBeat, declared at the top of this file.