trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
/system shows the last 20 idle loop-lag readings against the 100 ms bar, each over it named by its `loopWorstWhat`
3 of 3 done
0 open · 3 merged in 7 days · moved
Everything beneath it is done.
Merged in 7 days
- The tty registry, the cell watcher and the app runtime run their timers inside `during`, and a test finds any server timer outside it
- No background job holds the loop longer than 50 ms in one synchronous slice on a busy fixture, and a test times each one
- A loop stall over 200 ms is named by what ran: route or job, its ms, the last hour's worst on /system
Issues
None open.