I was comparing old and new logs to see if the CPU is more overloaded with my new config, and finally realized that the variable is simply unable to convey the actual CPU load. I currently see 127.5% for all datapoints, which is conveniently an 8-bit unsigned integer scaled to 0.5% (255 * 0.5% = 127.5%)
FWIW older configs of mine would sometimes dip to 120% (esp when RPM dropped, much more RPM related than wheel speed), so things have definitely gotten worse; also max load is now over 500%, while before it was “only” 169%.
The Max CPU Load also takes communication with the Client app into account. If you perform any CPU-intensive operation, such as loading a project, it may show a much higher value.
That probably applies for the over 500% case, as that day I was constantly loading new tunes and never cutting power. A better comparison would be a race weekend where it hit 211%, and I never connected the laptop.
Over the past few days, we’ve performed a firmware audit and performance profiling and identified several hotspots. To improve ECU performance, we released an update today with several performance optimizations.
As you mentioned, the ECU Performance CPU load channel is limited to 127%. However, there is a second channel that does not saturate: ECU Performance CPU delta time. This channel shows how often the main ECU thread is executed.
Link to update: New EMU PRO software version 261.3 beta