You are here: Home / Projects / QA Farm Realtime / 
2017-06-28 - 10:44

Dates and Events:

Breaking News:

2016-11-12 12:00

Raspberry Pi and real-time Linux

Let's have a look at the OSADL QA Farm data

2016-09-17 12:00

Preemption latency of real-time Linux systems

How to measure it – and how to fix it, if it's too high?

2014-11-18 00:00

Linux real-time: New stable release available -

but next one depends on more support from industrial users

OSADL Projects

OSADL Realtime QA Farm

About - Hardware - CPUs - Benchmarks - Graphics - Benchmarks - Kernels - Boards/Distros - Latency monitoring - Latency plots - System data - Profiles - Compare - Awards

Continuous worst-case latency monitoring

Wakeup latency of all systems - Real-time optimization - Peer-to-peer UDP duplex link - Powerlink - Ethercat - kvm - Sleep states

The newly available long-term monitoring of a system's worst-case interrupt and scheduling latency permits to record the latency of every single wakeup sequence of real-time processes throughout the uptime of the system. The plot below is generated at one of the OSADL testing labs and updated every couple of minutes. Background, kernel configuration and other details of internal latency monitoring are outlined in this abstract and explained in more detail in this paper (PDF format) of the Twelfth Real Time Linux Workshop.

Last update 1 minute ago

Continuous worst-case latency monitoring
Please note that the recorded values represent maxima of 5-min intervals. Thus, the data in the columns labeled "Min:" and "Avg:" should not be considered; the only relevant result is the maximum of consecutive 5-min maxima at the rightmost column labeled "Max:".

Generation of CPU load

Between 7 a.m. and 1 p.m. and between 7 p.m. and 1 a.m., a simulated application scenario is running using cyclictest at priority 99 with a cycle interval of 200 µs and a user program at normal priority that creates burst loads of memory, filesystem and network accesses. The particular cyclictest command is specified in every system's profile referenced above and on the next page. The load generator results in an average CPU load of 0.2 and a network bandwidth of about 8 Mb/s per system. Histogram data obtained from the cyclictest runs are used to create latency plots (aka Linux real-time plots) that are also referenced above and on the next page. Profiles and latency plots are updated twice a day.