Timing analysis

Explaining the concept of "execution time"

The execution time of a piece of code (say an RTOS task) is the amount of time that the processor spends executing that code. Execution time must exclude any time spent doing "other things" such as handling interrupts and, in the case of RTOS-based systems, executing other tasks. The concept is different to elapsed or "wall clock time". This measures how long the task takes from beginning to end, ignoring internal issues like context switches and interrupts. Yet another name for elapsed time is "response time".
Read More

Demonstrating how to “Rewind” backwards and forwards through recorded traces with RapiTime 2.3

Rapita’s Dr Paul Emberson recently travelled to Cambridge to demo one of the new features from the latest version of RapiTime at The Embedded Masterclass 2010. Here he explains his thoughts on the day and the emerging benefits of the new software.
Read More

Understanding the value of WCET optimisation within high-integrity real-time software

High-integrity software is typically thought of as being carefully constructed according to rigorous development procedures that primarily ensure its functional correctness. One casualty of this process can be run-time performance but, given the relatively small number of units being produced, the run-time performance can be addressed by over-specifying the hardware.
Read More

Pages