Loading Sample Trace File for Analysis

NOTE If a large .dat file is imported, the -graph and table response time will slow down until the large NPI file is saved. -Saving the NPI file will be performed in the background and cannot be -canceled.

NOTE You do not necessarily need to collect +the performance data by using PI Profiler on the device, but you can also do +profiling remotely, directly from the PI Wizard in Carbide.c++. For more +information, see Collecting Profiler +Data Remotely.

Importing a profiler data file will vary depending on if your application was built by Carbide.c++ or is a standalone application. To find the binaries @@ -34,32 +35,41 @@ Profiler application when capturing your application data in a profiler data file.

NOTE If a large .dat file is imported, the +graph and table response time will slow down until the large NPI file is saved. +Saving the NPI file will be performed in the background and cannot be +canceled.

Importing a Profiler Data File

Select Performance - Investigator Data

Select File > Import... from Carbide.c++ to display - Import dialog box (Figure 1), and select Performance Investigator Data and - click Next.

Figure 1. Carbide.c++ Import window

Start the import + wizard form the Carbice.c++ toolbat by selecting Carbide + > Performance Investigator
Select Profiler Data File(s) +
First use the radio buttons and select to get profiler data From + File System.
+
NOTE Use the From Device via + TraceViewer option if you want to collect new profiler data + remotely from the device. For more information, see Collecting Profiler Data + Remotely.

Select .dat file(s) to the From File System list by selecting either
- Add File and browsing to the file, or
- Add Directory and browsing to the directory you want to import files from.
- The .dat file(s) will be converted to a format displayable by the - Carbide.c++ analyzer and assigned the .npi extension.
- Use the Remove button to remove one file from the + list, or
- Use the Remove All button to clear all files from + the list.
+
The .dat file(s) will be converted to a format displayable by the + Carbide.c++ analyzer and assigned the .npi extension.

After selecting the file, the PI views included in the analysisfor filename.dat table will display a list of available views, according to the trace types available @@ -69,9 +79,11 @@ you can de-select the types you do not wish to include in the analysis. The CPU load view is a mandatory analysis and cannot be de-selected.
The trace types/views are selected separately for each .dat file.

Click Next to continue.

After selecting the files and views, click Next to + continue.

Figure 2. Select Profiler Data File

Select Known Available @@ -98,9 +110,8 @@ in remaining pages, since there is no previous import related to the new workspace. For a new imported .dat file, a new output file name will be generated based on this input file name (+ (digit) + .npi).
-
-
Figure 3. Enter known Available - Information
+

+
Figure 3. Enter known Available Information
If Both or the ROM image symbol file option is selected, the Select build files @@ -148,31 +159,60 @@
Select Output File and Project

-
Use the Output File and Project page to import the .dat file into an +
Use the Output File and Project page to import the *.npi file into an existing project or create a new empty project.
+
NOTE If you used remote profiling for collecting profiler + data from the device, the original *.dat file will also be included in the + selected project.
+

Figure 7. Enter Output File and Project Information
-
Click Finish to create the *.npi file.
+
Click Finish to create the *.npi file. +
NOTE Carbide.c++ reserves a large block of memory for the + Java Virtual Machine (JVM) to run the whole IDE. However, in some cases, + where Profiler trace log is too long in time and/or CPU load has been + extensively high over the use case, the trace import process may fail due + to out-of-memory situation. The out-of-menory may also lead to instability + issues with Carbide itself, but an error message will be always be shown: + Multiple problems have occurred. Jave heap space.
+ This problem can be avoided by keeping the profiled use cases shorter (the + recommendation is maximum 5 minutes), and by selecting only those Profiler + plug-ins that are needed for analysing the use case. Shorter use cases (in + time) and smaller amount of selected profiler plug-ins also ease up the + analysis phase, since it is easier to a browse shorter set of data and to + pinpoint the possible performance issues within the trace.
+ If you need to analyse longer use cases, there are also other tools + available for long-period-testing (LPT). For example, you can run the Nokia + Energy Profiler (NEP) directly on target and it can be used for LPT type of + use cases.
+

If Instructions executed has been selected as one of the trace, a the dialog below is displayed during PIAnalyser file import (once for each file f several are imported):
+ src="../../reference/analyzer/images/MIPS_speed_dialog.png" alt="">

-
If you imported only one file, PIAnalyser will open showing the views - selected for that file. -
If you imported several files, a project will be opened to the - Carbide Project Explorer where you can choose the file to - be viewed with PIAnalyser.
+
Performance Investigator view will open with the + imported files listed in it. A project will also be opened to the + Carbide Project Explorer including the imported files. +
If you imported only one file, PIAnalyser will also open showing the + views selected for that file. If you imported several files, you can open + any one of them by double-clicking the file name in the Performance + Investigator view or in the Project Explorer.