Performance comparision between IPC@CHIP family
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 |
Interrupt latency
The interrupt handler latency is the 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 |
TCP echo
A TCP Echo client application, running on Win2000 (AMD Athlon PC, 1GHz) establishes a TCP connection to an IPC@CHIP (SC12 or SC13) 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 only of receiving data from IPC@CHIP.
Send only : Measures the throughput, if the IPC@CHIP only sends 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 |
78 | 155 | 145 |
| SC13 100 Mbit/s |
212 | 443 | 406 |
UDP echo
An UDP Echo client application, running on Win2000 (AMD Athlon PC, 1GHz) sends UDP datagrams of different data sizes to an IPC@CHIP (SC12 or SC13) 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 (Win2000 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.
End of document