@CHIP-RTOS - Performance comparision between IPC@CHIP® family
IPC@CHIP® Documentation Index
RTOS task switch time
The following diagramm and C code shows how the measured values were calculated.
void huge taskA(void)
{
RTX_Sleep_Request();
}
void huge taskB(void)
{
RTX_Restart_Task (taskAID);
RTX_Wakeup (taskAID);
}
void main (void)
{
//...
result = RTX_Create_Task_Without_Run(&taskAID , &taskAdefblock);
RTX_Sleep_Time(10);
result = RTX_Create_Task(&taskBID , &taskBdefblock);
//...
}
| T1 | T2 | T3 | T4 | |
| SC12 | 104 µs | 80 µs | 100 µs | 60 µs |
| SC13/SC11 | 35 µs | 35 µs | 36 µs | 26 µs |
| SC13-LF/SC11-LF | 36 µs | 40 µs | 42 µs | 29 µs |
| SC123/SC143/SC23/SC24 | 8,2 µs | 8,2 µs | 9,0 µs | 6,4 µs |
Interrupt latency
The interrupt handler latency is the typical time from the processor's first response to an interrupt request signal through to the first useful instruction inside of the user interrupt service procedure.The user interrupt service procedure can be of type HW API or RTX.
| HW API handler latency | RTX handler latency | |
| SC12 | 84 µs | 90 µs |
| SC13/SC11 | 21 µs | 25 µs |
| SC13-LF/SC11-LF | 22 µs | 26 µs |
| SC123/SC143/SC23/SC24 | 6,5 µs | 7,3 µs |
TCP echo
A TCP Echo client application, running on WinXP (Intel Pentium IV, 2,8 GHz) establishes a TCP connection to an IPC@CHIP® (SC12, SC13, SC13-LF, SC123/SC143, SC23/SC24) TCP Echo server application. The TCP server echoes the incoming data back to the client. The client application measures the response time and calculates the amount of databytes in KBytes/sec, which the IPC@CHIP® is able to echo back to the client.The tests were made with a datasize of 10 MBytes.
Echotest : Measure the throughput of sending and receiving echo data.
Receive only: Measure the throughput with the IPC@CHIP® only receiving data.
Send only : Measures the throughput with the IPC@CHIP® only sending data.
This test was made under special test conditions. We cannot guarantee that the measured performance results are achievable on other test environment and conditions.
| Echo transfer rate KByte/s |
Receive only transfer rate KByte/s |
Send only transfer rate KByte/s |
|
| SC12 10 Mbit/s, RTOS V1.25 |
98 | 184 | 165 |
| SC13-LF 100 Mbit/s, RTOS V1.25 |
263 | 574 | 443 |
| SC13 100 Mbit/s, RTOS V1.25 |
287 | 610 | 488 |
| SC123/SC143/SC23/SC24 100 Mbit/s, RTOS V1.20 |
697 | 1395 | 1220 |
UDP echo
An UDP Echo client application, running on WinXP (Intel Pentium IV, 2,8 GHz) sends UDP datagrams of different data sizes to an IPC@CHIP® (SC12, SC13, SC13-LF, SC123/SC143, SC23/SC24) UDP Echo server application. The UDP server echoes the incoming datagramms back to the client. The client application measures the response time and calculates the amount of databytes in KBytes/sec, which the IPC@CHIP® is able to echo back to the client in dependency of the datagram size. The communication peers (WinXP PC and IPC@CHIP®) are connected with a "Twisted pair crossover cable" to avoid disturbtion by other network traffic.This test was made under special test conditions. We cannot guarantee that the measured performance results are achievable on other test environment and conditions.
| UDP Echo 1472 bytes KByte/s |
|
| SC12 10 Mbit/s, RTOS V1.25 |
107,81 |
| SC13-LF 100 Mbit/s, RTOS V1.25 |
370,88 |
| SC13 100 Mbit/s, RTOS V1.25 |
409,69 |
| SC123/SC143/SC23/SC24 100 Mbit/s, RTOS V1.20 |
918,56 |
End of document