What can cause long simulations times with large "self time" in Simulink Profiler for models or model references.
8 views (last 30 days)
Show older comments
MathWorks Support Team
on 2 Dec 2025 at 0:00
Edited: MathWorks Support Team
on 2 Dec 2025 at 19:08
I have a model that simulates slowly. My model has many signals, many of them multidimensional or bus signals. When I simulate with Simulink Profiler, it does not show one clear block that is causing problems. Much of the time is "self time" in the model itself or model references. What could be causing this?
Accepted Answer
MathWorks Support Team
on 2 Dec 2025 at 0:00
Edited: MathWorks Support Team
on 2 Dec 2025 at 19:08
This could be time Simulink spends on diagnostics such as "Simulation Range Checking" and "Inf or NaN block output". Try disabling some of the run-time diagnostics that scale with the number of signals and see if that improves performance.
Also inspect the number of warnings being thrown by your model. Throwing warnings can be expensive and blocks simulation execution. If you have hundreds or thousands of warnings, consider addressing the root issue or disabling diagnostics to reduce them.
Both running diagnostic checks and throwing warnings are two common reasons for "self time" to be large but not the only ones. If you need additional assistance locating the root cause of large "self time" for a model, consider creating a case with MathWorks Technical Support.
0 Comments
More Answers (0)
See Also
Categories
Find more on Test Model Components in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!