...
The CPU usage progress bar will turn Red, indicating that the CPU usage has exceeded 100 %. If the overflow condition is transient in nature, it is possible that the cpu bar may not show this condition.
The overflow detection LED (red dot) in the top right corner turns ON. The LED will stay ON until the Design is stopped, thus alerting the user of the overflow in the current run.
The CPU overflows counter on the top right corner counts the number of overflows detected across the layout (including clock divided sublayouts) until the Design is stopped. This count indicates that one or more overflows happened since the last time AWE Server queried the target for profiling values (by default this is done at 10 Hz). In theory the server could have missed some overflow events occurring at the target between the last query and the current query. As a result, this counter may not reflect the exact number of overflows occurring on the target.
...
Note: This feature is currently supported only for most accurate in embedded AWE Core based targets and is not supported on Native. Profiling support for AWE Core OS with multiple CPUs can be enabled with CPU Affinities as , but CPU loading and actual number of overflows may not be correct in extreme circumstances; highly buffered applications with spiky CPU usage for example. CPU overflows on the Native target will be least accurate because of thread / CPU interaction outside of the control of AWE Server. Using CPU affinity to increase the accuracy of this feature for AWE Core OS targets is described in https://documentation.dspconcepts.com/awe-designer/latest-version/profiling-in-audio-weaver-tips-and-tricks.
...