oschaaf
commented
5 years ago Part of this was done in v0.1, by using a more sane 0.5 second default and testing the execution path (and bugfixing an assert there) when a worker would be ready to start after its designated starting time.
This reduced the need for being able to configure this explicitly greatly, but I feel there's still something to say for exposing the option later on.
Currently workers in Nighthawk spend two seconds in a spin/yield loop, polling the clock for assessing time-to-start. This should be configurable, and the default can probably be much shorter.