lumiera_/tests/vault/gear
Ichthyostega 54e489b9b6 Scheduler-test: define criterion for breaking point
This statistical criterion defines when to count observed Scheduler performance
as loosing control. The test is comprised of three observations, which
all must be confirmed:

- an individual run counts as accidentally failed when the execution slips
  away by more than 2ms with respect to the defined overall schedule.
  When more than 55% of all observed runs are considered as failed,
  the first condition is met
- moreover, the observed standard derivation must also surpass the
  same limit of > 2ms, which indicates that the Scheduling mechanism
  is under substantial strain (on average, the slip is ~ 200µs)
- the third condition is that the ''averaged delta'' has surpassed
  4ms, which is 2 times the basic failure indicator.

These conditions are based on watching the Scheduler in operation;
typically all three conditions slip away by large margin after a
very narrow yet critical increase in the stress level.

Using three conditions together should improve robustness; often
the problems to keep up with the schedule build up over some parameter
range, yet the actual decision should be based on complete loss of control.
2024-01-03 21:11:20 +01:00
..
activity-detector-test.cpp Scheduler-test: rework handling of notifications in the Activity-Language 2023-12-16 23:47:50 +01:00
activity-detector.hpp Scheduler-test: rework handling of notifications in the Activity-Language 2023-12-16 23:47:50 +01:00
block-flow-test.cpp Scheduler-test: address defects in memory manager 2023-12-27 00:16:03 +01:00
scheduler-activity-test.cpp Scheduler-test: rework handling of notifications in the Activity-Language 2023-12-16 23:47:50 +01:00
scheduler-commutator-test.cpp Scheduler-test: adapt tests to changed logic at entrance 2023-12-27 00:16:03 +01:00
scheduler-invocation-test.cpp Scheduler: reconciled into clearer design 2023-11-04 04:49:13 +01:00
scheduler-load-control-test.cpp Scheduler: connect BlockFlow capacity announcement 2023-11-10 23:52:20 +01:00
scheduler-service-test.cpp Scheduler-test: build configurable measurement setup 2024-01-03 02:18:15 +01:00
scheduler-stress-test.cpp Scheduler-test: build configurable measurement setup 2024-01-03 02:18:15 +01:00
scheduler-usage-test.cpp Scheduler: plan for integration 2023-10-20 00:59:50 +02:00
special-job-fun-test.cpp Scheduler-test: a helper for one-time operations 2023-12-08 03:16:57 +01:00
stress-test-rig.hpp Scheduler-test: define criterion for breaking point 2024-01-03 21:11:20 +01:00
test-chain-load-test.cpp Scheduler-test: build configurable measurement setup 2024-01-03 02:18:15 +01:00
test-chain-load.hpp Scheduler-test: build configurable measurement setup 2024-01-03 02:18:15 +01:00
work-force-test.cpp Scheduler-test: implement contention mitigation scheme 2023-12-20 20:25:17 +01:00