Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Generate, Save and Load Profile Reports
When you profile the execution of your MS Native Windows application, the Profiler generates a report in the Call Stack that shows how functions are called in relation to the profiled application; for example, how one function might be taking most of the overall time recorded, and what contributions are made by the subfunctions that function calls. You have a number of options for reviewing and sharing the resulting report. You might:
| · | View the report immediately, in detailed or summary form |
| · | File the report in binary or xmi format |
| · | Reload the report at a later time |
| · | Refine the information displayed in the report |
| · | Distribute the report as a Team Review resource |
| · | Attach the report as a document to an Artifact element |
Access Analyzer | Profiler (execute): View Report
Options
Action |
Detail |
See also |
||||
|---|---|---|---|---|---|---|
Display Report |
When you have run the Profiler, click on the
This report can be very detailed, especially if every level is expanded. You can display a summary of the report by clicking on the Summary Report tab of the Call Stack.
You can filter and reorganize the information in the report, in the same way as you do for the results of a Model Search.
|
|
||||
Show or hide unknown frames
|
By default the report excludes unknown function calls and frames in the call tree. Click on the |
|
||||
Display the previous or next incidence of a function
|
When you select a node representing a function, and that function call is present in more than one stack, you can click on the |
|
||||
Set a Node as the root
|
If you want to examine a deeply-nested branch, you can make it the root node of the report. To do this, click on the node and click on the
|
|
||||
Reset the Root Node |
To return the report to displaying the branch from the node on which the report was originally generated, click on the
|
|
||||
Generate a Sequence Diagram |
You can generate a Sequence diagram from any node in the Profiler report. To do this, either:
The generated Sequence diagram reflects all activity resulting from the selected node. It is created as a child diagram of the Interaction corresponding to the node, and is immediately displayed in the Diagram View.
|
|
||||
Save Report to File |
Either:
The Save As dialog displays. Browse to the appropriate file location and, in the File name field, type the file name. In the Save as type field, select the file type you want to use, either binary (.ssprf) or .xmi. Click on the Save button.
|
|
||||
Load a Saved Report |
Click on the The Open dialog displays, on which you browse for and select the report file. Click on the Open button; the Call Stack opens or refreshes with the loaded report.
|
|
||||
Generate a Function Line report |
In the Sampler report, right-click on the name of the function to analyze, and select the Create Line report for function menu option. Once the Profiler binds the method, the line report is opened on the Sampler Report window.
|
|||||
Make Report a Team Review Resource |
You can save any current report as a resource for a Category, Topic or Post in the Team Review to share and review at any time, as it is saved with the model. The report can also be compared with future runs. To begin this process, select the menu option Team Review Context Menu | Share Resource | Add Active Profiler Report.
|
|
||||
In the Project Browser, select the Package or element under which to create the Artifact element. On the Call Stack window showing the report, right-click and select the Save Report to Artifact context menu option. You are prompted to provide a name for the report (and element); type this in and click on the OK button. The Artifact element is created in the Project Browser, underneath the selected Package or element. If you add the Artifact to a diagram as a simple link, when you double-click on the element the Call Stack window displays, showing the saved report.
|
Notes
| · | If you add the Profiler report to an Artifact element and also attach a linked document, the Profiler report takes precedence and is displayed when you double-click on the element; you can display the linked document using the Edit Linked Document context menu option |
Learn more
Learning Center topics
| · | Alt+F1 | Enterprise Architect | Execution Analysis | Profiling Native Code | View Report |
| · | Alt+F1 | Enterprise Architect | Execution Analysis | Profiling Native Code | Load Report from Disk |
