|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> |
|
5 <title>Collecting profiler data remotely</title> |
|
6 <link href="../../../book.css" rel="stylesheet" type="text/css"> |
|
7 </head> |
|
8 |
|
9 <body> |
|
10 <h2>Collecting Profiler Data Remotely</h2> |
|
11 |
|
12 <p>Instead of collecting performance data with PI Profiler on the device and |
|
13 importing it to Carbide.c++, you can also collect performance data directly |
|
14 from Carbide. The PI Import Wizard offers the option of collecting profiler |
|
15 data remotely from a device via a TraceViewer connection.</p> |
|
16 |
|
17 <p>To collect profiler data remotely, perform the following steps.</p> |
|
18 |
|
19 <div class="step"> |
|
20 <h3>Importing a Profiler Data File</h3> |
|
21 |
|
22 <h5>Open Import Wizard</h5> |
|
23 |
|
24 <p>In Carbide.c++, select <strong>Carbide</strong> > <strong>Performance |
|
25 Investigator</strong>.</p> |
|
26 |
|
27 <h5><a name="Select_Profiler_Data_File" |
|
28 id="Select_Profiler_Data_File"></a>Select Profiler Data File(s)</h5> |
|
29 <ol> |
|
30 <li><a name="First" id="First">First use the radio buttons and select to get |
|
31 profiler data <strong>From Device via TraceViewer</strong></a> . |
|
32 <p class="note"><strong>NOTE</strong> Use the <strong>From File |
|
33 System</strong> option if you want to import existing PI Profiler data |
|
34 files. For more information see <a href="an_load_trace_files.htm">Importing |
|
35 Profiler Data files</a>.</p> |
|
36 <p>The Wizard automatically tries to fetch information on supported plugins |
|
37 from the connected device. If you already have set up a working connection, |
|
38 the plugins are listed in the <strong>Select Plug-ins for Tracing</strong> |
|
39 field. Otherwise you will get the below notice: </p> |
|
40 <p align="center"><img src="images/Import_wizard_error.png" alt=""></p> |
|
41 <p align="center" class="figure">Figure 2. Import wizard notice </p> |
|
42 <p>In this case, or if you want to change the settings, follow the |
|
43 instructions below:</p> |
|
44 <ul> |
|
45 <li>Select Connection settings to open the TraceViewer Connections |
|
46 Setting dialog. Select the connection you want to use or create a new |
|
47 one. For more information, see TraceViewer <a |
|
48 href="../../../../com.nokia.traceviewer.help/html/reference/preferencesconnection.htm">Connection |
|
49 Settings</a>. |
|
50 <p class="note"><strong>NOTE</strong> You can use a USB or a TCP/IP |
|
51 Musti connection, but for profiling several samplers Musti is |
|
52 recommended due the too high amount of data.</p> |
|
53 </li> |
|
54 <li>Click <strong>OK</strong> in the Connection Setting dialog to save |
|
55 the settings and exit. |
|
56 <p>The selected connections is now shown below the <strong>Connections |
|
57 Settings</strong> button.</p> |
|
58 </li> |
|
59 <li>Click <strong>Refresh Plug-ins List</strong> . |
|
60 <p>The Wizard fetches the information on supported plugins and updates |
|
61 them to the <strong>Select Plug-ins for Tracing</strong> list.</p> |
|
62 <p align="center"><img src="images/PI_Wizard_Trace.png"></p> |
|
63 <p align="center" class="figure">Figure 3. Select Profiler Data File</p> |
|
64 </li> |
|
65 </ul> |
|
66 </li> |
|
67 <li><a name="Select" id="Select">Select the plug-ins you want to trace from |
|
68 the list</a>.</li> |
|
69 <li>Fill in the <strong>Profiler Data File Prefix</strong> you want to use as |
|
70 the name of the Profiler .dat file created.</li> |
|
71 <li>Click <strong>Start Tracing</strong>. |
|
72 <p>The wizard starts tracing. You can see the name of the created base64 |
|
73 encoded file (<em>*.base64</em>), the trace time (how long the trace has |
|
74 been running), as well as the size of the file in the <strong>Created |
|
75 Profiler Data File(s)</strong> list. </p> |
|
76 </li> |
|
77 <li id="Stop">Click <strong>Stop Tracing</strong> to finish tracing. |
|
78 <p>Tracing stops and the Wizard start converting the <em>*.base64</em> file |
|
79 into a <em>*.dat</em> file. You can follow the progress of the conversion |
|
80 from the progress bar. When the conversion is done, you can see the name of |
|
81 the file in the <strong>Created Profiler Data File(s)</strong> list change |
|
82 to <em>*.dat</em>.</p> |
|
83 </li> |
|
84 </ol> |
|
85 |
|
86 <p>It is possible to import several Profiler data files, so after the tracing |
|
87 and file conversion, you can either</p> |
|
88 <ul> |
|
89 <li>Run another trace, with or without changing the setting first, or</li> |
|
90 <li>Click <strong>Next ></strong> to continue importing the file(s). For |
|
91 instructions, see step 3 in <a |
|
92 href="an_load_trace_files.htm#Select_Known_Available_Information">Importing |
|
93 Profiler Data Files</a>. </li> |
|
94 </ul> |
|
95 </div> |
|
96 |
|
97 <p align="left"><strong>Related references</strong></p> |
|
98 <ul> |
|
99 <li><a href="an_load_trace_files.htm">Importing Profiler Data files</a></li> |
|
100 <li><a href="../../reference/analyzer/main_view.htm">Analyzer View</a></li> |
|
101 <li><a href="key_profile_pref.htm">Key Press Profile</a> </li> |
|
102 </ul> |
|
103 |
|
104 <div id="footer"> |
|
105 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
106 reserved. <br> |
|
107 License: <a |
|
108 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
|
109 </body> |
|
110 </html> |