Final Validation

Validates the overall performance improvement that your changes make in real-time execution time and accuracy.

If you have not validated the performance improvement resulting from other checks, use this check to perform a final validation of the changes to the model.

This check builds, downloads, and executes the real-time application. When the check passes, it displays the following information for the baseline and final validation runs:

  • Margin before CPU overload (0% indicates CPU overload) — A table containing, for each run, the real-time application task name, the sample rate, and the margin.

    Margin is the minimum value of headroom for a task over all the measured samples.

    Headroom is the time between the end of execution and the start of the next sample, as a percentage of sample time. For example, if the sample time is 1.2 ms and a task takes 0.93 ms to execute, the headroom is (1.2 - 0.93)/1.2, or 22.5%.

    As the margin approaches 0%, the application gets closer to overloading the CPU.

  • Average CPU Usage — Pie charts showing, for each run, the average CPU resources that the real-time application uses, as a percentage of available resources.

    The available CPU resources include all of the processors on a multicore target computer. For example, a single-tasking model running on a quad-core processor cannot exceed 25% CPU usage.

    The background task aggregates the CPU time for all operating system tasks that are not related to application execution. These tasks include updating the target screen, communicating with the development computer, and so on. It also includes the time that the CPU is idle.

See Also