RTAI Testsuite LiveCD
Collecting hardware's hard real-time performance data
| name | value |
| Timestamp of submission: | 2009-05-19 15:58:44-06 |
| Submitter: | mbrzeski[at]uwm[dot]edu |
| Machine ID: | Linus19 |
| Message: | |
| LiveCD version: | 0.16 |
| Linux version: | 2.6.10-adeos-pmmx#9 Wed Apr 20 16:57:51 CEST 2005 |
| ADEOS version: | 2.6r10c3/x86 |
| RTAI version: | 3.2-test3 |
| Fusion version: | |
Hardware
CPU
| name | value |
| CPU name: | Cx486DLC |
| CPU vendor: | Geode by NSC |
| CPU family: | 5 |
| CPU model: | 1 |
| CPU stepping: | 0 |
| CPU cache: | |
| CPU frequency: | 366.74 |
PCI devices
The following table shows all PCI devices that were plugged
in the testmachine during the testrun.
| category | name |
| Ethernet controller |  Intel Corp. 82559ER (rev 10) |
| VGA compatible controller | National Semiconductor Corporation CS5535 Video |
| Host bridge | National Semiconductor Corporation CS5535 Host bridge (rev 21) |
| Multimedia audio controller | National Semiconductor Corporation CS5535 Audio |
| IDE interface | National Semiconductor Corporation CS5535 IDE |
| USB Controller | National Semiconductor Corporation CS5535 USB (rev 06) |
| ISA bridge | National Semiconductor Corporation CS5535 ISA bridge (rev 13) |
Testresults
BYTE nbench benchmark
The following results were acquired using the Linux port of
release 2 of BYTE Magazine's BYTEmark benchmark program.
| name | result |
| integer: | 0.203 |
| floating point: | 0.231 |
| memory: | 0.187 |
RTAI testsuite
UP scheduler - latency
The difference in time between the expected switch
time and the time when a task is actually called by the scheduler is
measured. For this test the RTAI UP scheduler is used.
RTAI README file
| name | result |
| RTAI UP latency minimum: | 2879 ns |
| RTAI UP latency average: | 5865 ns |
| RTAI UP latency maximum: | 28287 ns |
| RTAI UP latency runtime: | 227 s |
LXRT scheduler - latency
The difference in time between the expected switch
time and the time when a task is actually called by the scheduler is
measured. For this test the RTAI LXRT scheduler is used.
RTAI README file
| name | result |
| RTAI LXRT latency minimum: | 6471 ns |
| RTAI LXRT latency average: | 9874 ns |
| RTAI LXRT latency maximum: | 31925 ns |
| RTAI LXRT latency runtime: | 255 s |
UP scheduler - preemption
The following table shows the results of a stress test aimed at
verifying that the schedulers preempt well under intense load.
It is a simple test that combines the latency calibration task with a fast and slow task in such a way to have two levels of preemption, nesting on an
odd
number of tasks.
It shows the maximum jitter of the fast task, which has the second
highest priority, and of the slow which has the lowest priority.
Reasonable jitters are a clear indication of preemption.
RTAI README file| name | result |
| RTAI UP preempt fastjit: | 18013 ns |
| RTAI UP preempt slowjit: | 20903 ns |
| RTAI UP preempt runtime: | 142 s |
LXRT scheduler - preemption
The following table shows the results of a stress test aimed at
verifying that the schedulers preempt well under intense load.
It is a simple test that combines the latency calibration task with a fast and slow task in such a way to have two levels of preemption, nesting on an
odd
number of tasks.
It shows the maximum jitter of the fast task, which has the second
highest priority, and of the slow which has the lowest priority.
Reasonable jitters are a clear indication of preemption.
RTAI README file| name | result |
| RTAI LXRT preempt fastjit: | 33825 ns |
| RTAI LXRT preempt slowjit: | 25841 ns |
| RTAI LXRT preempt runtime: | 193 s |
| name | result |
| RTAI Fusion klatency minimum: | 5786 ns |
| RTAI Fusion klatency average: | 8352 ns |
| RTAI Fusion klatency maximum: | 38823 ns |
| RTAI Fusion klatency runtime: | 21 s |
