3 Click Start Profiling.
While the Profiler is running, the Profile time indicator is green and the number of
seconds it reports increases. The Profile time indicator appears at the top right of
the Profiler window.When the Profiler finishes, the Profile time indicator turns black and shows the
length of time the Profiler ran. The statements you profiled display as having been
executed in the Command Window.This time is not the actual time that your statements took to run. It is the time
elapsed from when you clicked Start Profiling until the profiling stops. If the time
reported is very different from what you expected (for example, hundreds of seconds
for a simple statement), you might have profiled longer than necessary. This time
does not match the time reported in Profile Summary report statistics, which is based
on performance clock time by default. To view profile statistics using a different
type of clock, use the profile function instead of the Profiler.
4 When profiling is complete, the Profile Summary report appears in the Profiler
window. For more information, see “Profile Summary Report” on page 28-8.
Profile Multiple Statements in Command Window
To profile more than one statement:
1 In the Profiler, click Start Profiling. Make sure that no code appears in the Run this
code field.
2 In the Command Window, enter and run the statements you want to profile.
3 After running all the statements, click Stop Profiling in the Profiler, and view the
Profile Summary report.
Profile a User Interface
You can run the Profiler for a user interface, such as the Filter Design and Analysis tool
included with Signal Processing Toolbox. Or, you can profile an interface you created,
such as one built using GUIDE.
To profile a user interface:
Profile to Improve Performance