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

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

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

Function Documentation

_uTicks()

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

inline

Definition at line 120 of file load-controller.hpp.

References _uTicks().

Referenced by _uTicks().

Here is the call graph for this function:

Here is the caller graph for this function:

Variable Documentation

SLEEP_HORIZON

Duration SLEEP_HORIZON {_uTicks (20ms)}

schedules beyond that horizon justify going idle

Definition at line 126 of file load-controller.hpp.

WORK_HORIZON

Duration WORK_HORIZON {_uTicks ( 5ms)}

the scope of activity currently in the works

Definition at line 127 of file load-controller.hpp.

NEAR_HORIZON

Duration NEAR_HORIZON {_uTicks (50us)}

what counts as "imminent" (e.g. for spin-waiting)

Definition at line 128 of file load-controller.hpp.

STANDARD_LAG

Duration STANDARD_LAG {_uTicks(200us)}

Experience shows that on average scheduling happens with 200µs delay.

Definition at line 129 of file load-controller.hpp.

LAG_SAMPLE_DAMPING

const double LAG_SAMPLE_DAMPING = 2

smoothing factor for exponential moving average of lag;

Definition at line 131 of file load-controller.hpp.