...it is clear that there must be a way to flush the scheduler queues an thereby silently drop any obsoleted or irrelevant entries. This topic turns out to be somewhat involved, as it requires to consider the deadline (due to the memory management, which is based on deadlines). Furthermore there is a relation to yet another challenging conceptual requirement, which is the support for other operation modes beyond just time-bound rendering; these concerns make it desirable to expand the internal representation of entries in the queue. Concerns regarding performance are postponed deliberately, until we can demonstrate the Scheduler-Service running under regular operational conditions. |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-load-control-test.cpp | ||
| scheduler-service-test.cpp | ||
| scheduler-stress-test.cpp | ||
| scheduler-usage-test.cpp | ||
| work-force-test.cpp | ||