Simulink takes a long time to start a model with a Embedded Matlab block

I have an embedded matlab block that contains a decent amount of code. When I start the Simulink model, the status bar shows that it is compiling the embedded matlab block and it takes a really long time (like 30 minutes). Is there a way to debug why it takes the compiler so long and where it would be getting hung up or any optimizations I could do?

Answer 1

[Gillian Rosen]

Hi Thomas, 

I understand that an Embedded MATLAB block in your model is taking a long time (30 minutes) to compile every time you simulate your model, and you would like to debug this issue and find possible optimizations.

For debugging this issue, you can use the 'sldiagnostics' command to investigate which parts of the process are taking a long time. Since you are interested in debugging long compilation times, I suggest that you use this command with the 'CompileStats' option, as follows:  

>> sldiagnostics('myModel','CompileStats')

See the 'sldiagnostics' function documentation at the link below for more information:

http://www.mathworks.com/help/releases/R2010b/toolbox/simulink/slref/sldiagnostics.html

If your Embedded MATLAB block is not changing between runs of your simulation, you could place your Embedded MATLAB block into a model reference to speed up compilation. By default, referenced models will only be re-compiled if a change is detected. Here are some documentation links to get you started with model referencing:  

http://www.mathworks.com/help/releases/R2010b/toolbox/simulink/ug/bq_5wvg-1.html

http://www.mathworks.com/help/releases/R2010b/toolbox/simulink/gui/bq7cyf9-1.html

http://www.mathworks.com/help/releases/R2010b/toolbox/simulink/slref/modelvariants.html

[Thomas Marullo]

Thank you. This is exactly what I was looking for. My model spends the most time doing "Stateflow post-compile notify". Is there some documentation on what this is?

[Nick McDonough]

I am having a similar issue. The Stateflow post-compile notify is taking forever, but I don't know how to debug further....