Modelica Performance Analyzer¶

A common problem when simulating models in an equation-based language like Modelica is that the model may contain non-linear equation systems. These are solved in each time-step by extrapolating an initial guess and running a non-linear system solver. If the simulation takes too long to simulate, it is useful to run the performance analysis tool. The tool has around 5~25% overhead, which is very low compared to instruction-level profilers (30x-100x overhead). Due to being based on a single simulation run, the report may contain spikes in the charts.

When running a simulation for performance analysis, execution times of user-defined functions as well as linear, non-linear and mixed equation systems are recorded.

To start a simulation in this mode, turn on profiling with the following command line flag >>> setCommandLineOptions("--profiling=all")

The generated report is in HTML format (with images in the SVG format), stored in a file modelname_prof.html, but the XML database and measured times that generated the report and graphs are also available if you want to customize the report for comparison with other tools.

Below we use the performance profiler on the simple model A:

model ProfilingTest
  function f
    input Real r;
    output Real o = sin(r);
  end f;
  String s = "abc";
  Real x = f(x) "This is x";
  Real y(start=1);
  Real z1 = cos(z2);
  Real z2 = sin(z1);
equation
  der(y) = time;
end ProfilingTest;

We simulate as usual, after setting the profiling flag:

>>> setCommandLineOptions("--profiling=blocks+html")
true
>>> simulate(ProfilingTest)
record SimulationResult
    resultFile = "«DOCHOME»/ProfilingTest_res.mat",
    simulationOptions = "startTime = 0.0, stopTime = 1.0, numberOfIntervals = 500, tolerance = 1e-06, method = 'dassl', fileNamePrefix = 'ProfilingTest', options = '', outputFormat = 'mat', variableFilter = '.*', cflags = '', simflags = ''",
    messages = "LOG_SUCCESS       | info    | The initialization finished successfully without homotopy method.
LOG_SUCCESS       | info    | The simulation finished successfully.
Warning: empty y range [3:3], adjusting to [2.97:3.03]
Warning: empty y range [3:3], adjusting to [2.97:3.03]
Warning: empty y range [2:2], adjusting to [1.98:2.02]
Warning: empty y range [2:2], adjusting to [1.98:2.02]
Warning: empty y range [3:3], adjusting to [2.97:3.03]
Warning: empty y range [3:3], adjusting to [2.97:3.03]
stdout            | info    | Time measurements are stored in ProfilingTest_prof.html (human-readable) and ProfilingTest_prof.xml (for XSL transforms or more details)
",
    timeFrontend = 0.001316879,
    timeBackend = 0.210141619,
    timeSimCode = 0.007836814999999886,
    timeTemplates = 0.194077301,
    timeCompile = 1.198719753,
    timeSimulation = 0.220562457,
    timeTotal = 1.832804156
end SimulationResult;
"Warning: There are nonlinear iteration variables with default zero start attribute found in NLSJac0. For more information set -d=initialization. In OMEdit Tools->Options->Simulation->Show additional information from the initialization process, in OMNotebook call setCommandLineOptions(\"-d=initialization\").
Warning: The initial conditions are not fully specified. For more information set -d=initialization. In OMEdit Tools->Options->Simulation->Show additional information from the initialization process, in OMNotebook call setCommandLineOptions(\"-d=initialization\").
"

Profiling information for ProfilingTest¶

Information¶

All times are measured using a real-time wall clock. This means context switching produces bad worst-case execution times (max times) for blocks. If you want better results, use a CPU-time clock or run the command using real-time priviliges (avoiding context switches).

Note that for blocks where the individual execution time is close to the accuracy of the real-time clock, the maximum measured time may deviate a lot from the average.

For more details, see ProfilingTest_prof.xml.

Settings¶

Name	Value
Integration method	dassl
Output format	mat
Output name	ProfilingTest_res.mat
Output size	24.0 kB
Profiling data	ProfilingTest_prof.data
Profiling size	0 B

Summary¶

Task	Time	Fraction
Pre-Initialization	0.000201	3.08%
Initialization	0.000246	3.77%
Event-handling	0.000068	1.04%
Creating output file	0.000341	5.22%
Linearization		NaN%
Time steps	0.004709	72.11%
Overhead	0.000492	7.53%
Unknown	NaN	NaN%
Total simulation time	0.006530	100.00%

Global Steps¶

	Steps	Total Time	Fractio n	Average Time	Max Time	Deviati on
\|Graph thumbna il 999\|	499	0.00470 9	72.11%	9.43687 3747494 99e-06	0.00009 9790	9.57x

Measured Function Calls¶

	Name	Calls	Time	Fractio n	Max Time	Deviati on
\|Graph thumbna il functio n fun0\|\|Graph thumbna il count functio n fun0\|	Profil ingTest .f _	1512	0.00009 9929	1.53%	0.00000 0814	11.32x

Measured Blocks¶

	Name	Calls	Time	Fractio n	Max Time	Deviati on
\|Graph thumbna il eq0\|\| Graph thumbna il count eq0\|	` <#eq0 >`__	8	0.00014 5186	2.22%	0.00014 5375	7.01x
\|Graph thumbna il eq11\|\|Graph thumbna il count eq11\|	` <#eq1 1>`__	4	0.00000 4383	0.07%	0.00000 4464	3.07x
\|Graph thumbna il eq19\|\|Graph thumbna il count eq19\|	` <#eq1 9>`__	1006	0.00186 2326	28.52%	0.00004 2068	21.72x
\|Graph thumbna il eq21\|\|Graph thumbna il count eq21\|	` <#eq2 1>`__	1508	0.00148 9803	22.81%	0.00003 0987	30.37x

Equations¶

Name	Variables
eq0
eq1	y
eq2	s
eq3	z1
eq4
eq5	` <#var0>`__
eq6	` <#var0>`__
eq7	` <#var0>`__
eq8	` <#var0>`__
eq9	z2
eq10
eq11	x
eq12
eq13	z2
eq14
eq15	` <#var0>`__
eq16	` <#var0>`__
eq17	` <#var0>`__
eq18	` <#var0>`__
eq19	z1
eq20
eq21	x
eq22	der(y)
eq23

Variables¶

Name	Comment
y
der(y)
x	This is x
z1
z2
s

This report was generated by OpenModelica on 2022-07-22 22:56:33.

Genenerated JSON for the Example¶

Listing 9 ProfilingTest_prof.json¶

{
"name":"ProfilingTest",
"prefix":"ProfilingTest",
"date":"2022-07-22 22:56:33",
"method":"dassl",
"outputFormat":"mat",
"outputFilename":"ProfilingTest_res.mat",
"outputFilesize":24581,
"overheadTime":0.000492264,
"preinitTime":0.000201379,
"initTime":0.000245936,
"eventTime":6.7654e-05,
"outputTime":0.000341298,
"jacobianTime":1.3132e-05,
"totalTime":0.00652996,
"totalStepsTime":7.738e-06,
"totalTimeProfileBlocks":0.0035017,
"numStep":499,
"maxTime":9.979e-05,
"functions":[
{"name":"ProfilingTest.f","ncall":1512,"time":0.000099929,"maxTime":0.000000814}
],
"profileBlocks":[
{"id":0,"ncall":8,"time":0.000145186,"maxTime":0.000145375},
{"id":11,"ncall":4,"time":0.000004383,"maxTime":0.000004464},
{"id":19,"ncall":1006,"time":0.001862326,"maxTime":0.000042068},
{"id":21,"ncall":1508,"time":0.001489803,"maxTime":0.000030987}
]
}

Using the Profiler from OMEdit¶

When running a simulation from OMEdit, it is possible to enable profiling information, which can be combined with the transformations browser.

Figure 139 Setting up the profiler from OMEdit.¶

When profiling the DoublePendulum example from MSL, the following output in Figure 140 is a typical result. This information clearly shows which system takes longest to simulate (a linear system, where most of the time overhead probably comes from initializing LAPACK over and over).

Figure 140 Profiling results of the Modelica standard library DoublePendulum example, sorted by execution time.¶