RTC-latency test results _label1_



- the red reference line is an immaginary deadline, the number of "overruns" are the number of deadline misses
  actually this is set to 3*fragment latency (for examp   for example if RTC-HZ=512 (1.9ms period), then the deadline is set to 5.85ms)
- the white line is the actual scheduling latency, the ideal would be 1/RTCfrequency . (fragment latency)
- the green line is the time the CPU takes to execute an empty loop (which is calibrated at 80% of the fragment time)

  since the thread runs with SCHED_FIFO priority, if this time goes up, then the cause could be the DMA / PCI / ISA contention on the system bus, or busy kernel I/O routines
- the yellow reference line is the period of the RTC frequency (ideally the white line should stay close to yellow line)
- the white between +/-1ms is the % of time the total latency stays in the range between +/-1ms of the optimal latency.
- the white between +/-2ms is the % of time the total latency stays in the range between +/-2ms of the optimal latency.
- the green between +/-0.2ms is the % of time the CPU loop latency stays in the range between +/-0.2ms of the nominal CPU loop latency.
- the green between +/-0.1ms is the % of time the CPU loop latency stays in the range between +/-0.1ms of the nominal CPU loop latency.

X11 stress



/proc filesystem stress



disk write stress



disk copy stress



disk read stress