1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
2 |
|
3 <html> |
2 <html> |
4 <head> |
3 <head> |
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
4 <meta http-equiv="content-type" content="text/html; charset=UTF-8"> |
6 <title>Overview</title> |
5 <title>Overview</title> |
7 <link href="../../../book.css" rel="stylesheet" type="text/css"> |
6 <link href="../../../book.css" rel="stylesheet" type="text/css"> |
8 </head> |
7 </head> |
9 |
8 |
10 <body> |
9 <body> |
11 <h2>Overview</h2> |
10 <h2>Overview</h2> |
12 <p>The Performance Investigator is a software performance measurement tool. The Performance Investigator collects run-time information from your application and other software running on a Symbian OS enabled device, such as a Nokia S60 phone, or a SEMC device running UIQ. The recorded information is then analyzed in the Performance Investigator analyzer software running on a PC.</p> |
11 |
|
12 <p>The Performance Investigator is a software performance measurement tool. The |
|
13 Performance Investigator collects run-time information from your application |
|
14 and other software running on a Symbian OS enabled device, such as a Nokia S60 |
|
15 phone.. The recorded information is then analyzed in the Performance |
|
16 Investigator analyzer software running on a PC.</p> |
|
17 |
13 <p>Performance Investigator currently supports the following:</p> |
18 <p>Performance Investigator currently supports the following:</p> |
14 <ul> |
19 <ul> |
15 <li>Nokia devices running S60 3.0 and 3.1 </li> |
20 <li>Nokia devices running S60 3.0 and 3.1 </li> |
16 <li>SEMC devices running UIQ 3.0</li> |
21 <li>SEMC devices running UIQ 3.0</li> |
17 <li>Symbian TechView for Symbian OS 9.2, 9.3, 9.4, and 9.5</li> |
22 <li>Symbian TechView for Symbian OS 9.2, 9.3, 9.4, and 9.5</li> |
18 </ul> |
23 </ul> |
19 <p>The Performance Investigator collects performance data. It interrupts software execution at regular intervals and copies to memory the contents of some processor registers and the results of some Symbian OS calls.</p> |
24 |
|
25 <p>The Performance Investigator collects performance data. It interrupts |
|
26 software execution at regular intervals and copies to memory the contents of |
|
27 some processor registers and the results of some Symbian OS calls.</p> |
|
28 |
20 <p>The Performance Investigator contains two main parts:</p> |
29 <p>The Performance Investigator contains two main parts:</p> |
21 <ul> |
30 <ul> |
22 <li>First, on the target device is a user application called the Profiler. Installed with the Profiler is a device driver component that collects information from low-level (kernel and hardware-level) sources that are not generally accessed by application software. The Profiler acts as an interface to the device driver component and is required for its configuration, activation, and deactivation.</li> |
31 <li>First, on the target device is a user application called the Profiler. |
23 <li>Second, on the PC there is Performance Investigator code integrated with Carbide.c++. This software consists of an importer for processing profiler data and the Analyzer, which provides a user-friendly way to examine and analyze the run-time performance information.</li> |
32 Installed with the Profiler is a device driver component that collects |
|
33 information from low-level (kernel and hardware-level) sources that are not |
|
34 generally accessed by application software. The Profiler acts as an |
|
35 interface to the device driver component and is required for its |
|
36 configuration, activation, and deactivation.</li> |
|
37 <li>Second, on the PC there is Performance Investigator code integrated with |
|
38 Carbide.c++. This software consists of an importer for processing profiler |
|
39 data and the Analyzer, which provides a user-friendly way to examine and |
|
40 analyze the run-time performance information.</li> |
24 </ul> |
41 </ul> |
25 <p>The following figure illustrates the basic scenario to gather and analyze software performance data. The target device contains the actual performance measurement instrumentation referred to as the Profiler. The data file imported by Carbide.c++ is analyzed on a PC workstation independent of the target device.</p> |
42 |
26 <p align="center"><img src="../../images/overview.png" width="537" height="336"></p> |
43 <p>The following figure illustrates the basic scenario to gather and analyze |
27 <p class="figure">Figure 1. Performance Investigator Tool: profiler and analyzer</p> |
44 software performance data. The target device contains the actual performance |
28 <p>Performance measurements follow a pattern in which separate performance related activities are recorded to a profiler data file within the target device as distinct traces. Each trace represents an independent performance characteristic of the target device. When the profiler data file is imported by Carbide.c++, more information can be derived from the traces. Each trace can be independently analyzed. Furthermore, information gathered from the software at compile-time can be used in the analysis in order to exploit the cross-relations between elements of information available exclusively at run-time or at compile-time.</p> |
45 measurement instrumentation referred to as the Profiler. The data file imported |
|
46 by Carbide.c++ is analyzed on a PC workstation independent of the target |
|
47 device.</p> |
|
48 |
|
49 <p align="center"><img src="../../images/overview.png" width="537" |
|
50 height="336"></p> |
|
51 |
|
52 <p class="figure">Figure 1. Performance Investigator Tool: profiler and |
|
53 analyzer</p> |
|
54 |
|
55 <p>Performance measurements follow a pattern in which separate performance |
|
56 related activities are recorded to a profiler data file within the target |
|
57 device as distinct traces. Each trace represents an independent performance |
|
58 characteristic of the target device. When the profiler data file is imported by |
|
59 Carbide.c++, more information can be derived from the traces. Each trace can be |
|
60 independently analyzed. Furthermore, information gathered from the software at |
|
61 compile-time can be used in the analysis in order to exploit the |
|
62 cross-relations between elements of information available exclusively at |
|
63 run-time or at compile-time.</p> |
|
64 |
29 <p><strong>Related references </strong></p> |
65 <p><strong>Related references </strong></p> |
30 <ul> |
66 <ul> |
31 <li><a href="sw_performance.htm">Software Performance</a></li> |
67 <li><a href="sw_performance.htm">Software Performance</a></li> |
32 <li><a href="../../reference/profiler/profiler.htm">Profiler</a></li> |
68 <li><a href="../../reference/profiler/profiler.htm">Profiler</a></li> |
33 <li><a href="../../reference/analyzer/analyser.htm">Analyzer</a></li> |
69 <li><a href="../../reference/analyzer/analyser.htm">Analyzer</a></li> |
34 <li><a href="../../reference/abbrev.htm">Acronyms</a></li> |
70 <li><a href="../../reference/abbrev.htm">Acronyms</a></li> |
35 </ul> |
71 </ul> |
36 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
72 |
|
73 <div id="footer"> |
|
74 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
75 reserved. <br> |
|
76 License: <a |
|
77 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
37 </body> |
78 </body> |
38 </html> |
79 </html> |