sysperfana/perfinvestigator/com.nokia.carbide.cpp.pi.doc.user/html/reference/analyzer/main_view.htm
changeset 12 ae255c9aa552
parent 5 844b047e260d
equal deleted inserted replaced
11:5b9d4d8641ce 12:ae255c9aa552
     9 
     9 
    10 <body>
    10 <body>
    11 <h2>Analyzer View</h2>
    11 <h2>Analyzer View</h2>
    12 
    12 
    13 <p>The main analysis view is visible after trace data taken by Profiler has
    13 <p>The main analysis view is visible after trace data taken by Profiler has
    14 been imported into Carbide.c++ and opened with Analyzer. The thread load data
    14 been imported into Carbide.c++ and opened with Analyzer. Figure 1 is an example
    15 in the main analysis view is built from the address/thread trace. Other trace
    15 view of imported profiler data that has been opened with the analyzer,
    16 data is also shown in the main analysis view, such as dynamic binary support
    16 including memory and power usage information, with a time interval of 4 to 8
    17 trace and function call trace. Figure 1 is an example view of imported profiler
    17 seconds selected.The Interrups graph and Performance Counters graph have been
    18 data that has been opened with the analyzer, including memory and power usage
    18 minized.</p>
    19 information, with a time interval of 4 to 8 seconds selected.The Interrups
       
    20 graph and Performance Counters graph have been minized.</p>
       
    21 
    19 
    22 <p align="center"><img src="images/analyzer_mainview.png" width="679"
    20 <p align="center"><img src="images/analyzer_mainview.png" width="679"
    23 height="770"> </p>
    21 height="770"> </p>
    24 
    22 
    25 <p align="center" class="figure">Figure 1. Analyzer main view showing Thread,
    23 <p align="center" class="figure">Figure 1. Analyzer main view showing Thread,
    26 Memory, and Power graphs</p>
    24 Memory, and Power graphs</p>
    27 
    25 
    28 <p>The address/thread trace graph is the most generic and perhaps most
    26 <p>You can select a portion of the graph by clicking on the graph. The legend
    29 informative visual of the sampled data. The different colors represent
    27 table beneath the graph displays information about the currently selected part
    30 different items. Time is represented on the horizontal axis of the graph and
    28 of the graph. For example, thread load statistics are shown in the table if the
    31 share of CPU use is represented on the vertical axis. You can select Thread
    29 thread load graph is selected.</p>
    32 load, Binary load, or Function load by selecting the respective tabs at the
       
    33 bottom of the main view, as shown in Figure 2.</p>
       
    34 
    30 
    35 <p align="center"><img src="images/analz_loads_tabs.png" width="423"
    31 <p>You can use the buttons on the title bars to manipulate what is displayed in
    36 height="84"></p>
    32 Analyser. For more information, see <a href="GUI_tour.htm">Analyzer GUI
       
    33 Controls</a>. </p>
    37 
    34 
    38 <p align="center" class="figure">Figure 2. Selecting Threads, Binaries,
    35 <p>For more specific information on all the views and graps available in PI
    39 Functions, or Function Calls</p>
    36 Analyser, use the links below in Related references.</p>
    40 
       
    41 <p>Each of the lines in the thread table represents a single thread. The color
       
    42 codes in the thread list correspond to the colors in the thread load graphs.
       
    43 Therefore, each color in the thread load graph represents the load of its
       
    44 corresponding thread.</p>
       
    45 
       
    46 <p>You can select a portion of the graph by clicking on the trace graph. The
       
    47 legend table beneath the graph displays information about the currently
       
    48 selected part of the graph. For example, thread load statistics are shown in
       
    49 the table if the thread load graph is selected.</p>
       
    50 
    37 
    51 <p><strong>Related references</strong></p>
    38 <p><strong>Related references</strong></p>
    52 <ul>
    39 <ul>
    53   <li><a href="GUI_tour.htm">Analyzer GUI Controls </a></li>
    40   <li><a href="view_CPU.htm">CPU Views</a></li>
    54   <li><a href="thread_load.htm">Thread Load</a></li>
    41   <li><a href="view_memory_usage.htm">Memory Usage view</a></li>
    55   <li><a href="binary_load.htm">Binary Load</a></li>
    42   <li><a href="view_graphics_memory_usage.htm">Graphics Memory Usage
    56   <li><a href="function_load.htm">Function Load</a></li>
    43   view</a></li>
    57   <li><a href="function_calls.htm">Function Calls</a></li>
    44   <li><a href="view_power_usage.htm">Power Usage view</a></li>
       
    45   <li><a href="interrupts_view.htm">Interrupts view</a></li>
       
    46   <li><a href="view_performance_counters.htm">Performance Counters view</a></li>
       
    47   <li><a href="view_IPC.htm">Interconnect Performance Counters view</a></li>
       
    48   <li><a href="GUI_tour.htm">Analyzer GUI Controls</a></li>
    58 </ul>
    49 </ul>
    59 
    50 
    60 <div id="footer">
    51 <div id="footer">
    61 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights
    52 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights
    62 reserved. <br>
    53 reserved. <br>