Software timing requirements may be written in terms of both execution time (time spent actually executing a function) and response time (total clock time from start of execution to end of execution, some of which may be spent within other functions).
RVS helps you to analyze point-to-point response times through a flexible approach that lets you capture timing information across sequences you define in your code. This approach also lets you measure other timing metrics such as periodicity and separation, and capture timing measurements across specific sequences with multiple checkpoints.
To set this up, you simply need to define the points in your code across which you want to measure response times within the RVS Project Manager.
When you run your code, timing data will be collected and presented in your RVS report.
Feature applies to: