vault::gear::anonymous_namespace{load-controller.hpp} Namespace Reference

Functions
TimeValue	_uTicks (std::chrono::microseconds us)

Variables
const double	LAG_SAMPLE_DAMPING = 2
	smoothing factor for exponential moving average of lag;
Duration	NEAR_HORIZON {_uTicks (50us)}
	what counts as "imminent" (e.g. for spin-waiting)
Duration	SLEEP_HORIZON {_uTicks (20ms)}
	schedules beyond that horizon justify going idle
Duration	STANDARD_LAG {_uTicks(200us)}
	Experience shows that on average scheduling happens with 200µs delay.
Duration	WORK_HORIZON {_uTicks ( 5ms)}
	the scope of activity currently in the works