Hi, Please find attached the forte and quantify performance report for background properties capplet. Please get back to us in case you need additional information / data. Regards, Muktha and AnandTitle:
|
(version 1.0) 1. Component Summary
2. Brief Description of
Tests Done to Collect Performance Data
3. Data 2.1 Test: Background_01 As per the quantify data collected, the top five functions which consumed the maximum percentage of the total execution time, have been considered for the analysis. The forte leaks data showed a total of 16 MB leak when a JPEG image
file was set as the background, and the capplet was closed.
3.1.1 Forte Collect Data
3.1.2 Quantify Data
[1] Due to huge sizes of the er_print data for leaks, the data
in the attached gzipped files have been limited to the top 500 leaks
only. The complete leaks information is however available and can be provided,
if required.
4. Appendix 4.1 Forte data Data is collected using the 'collect' and 'er_print' forte profiling tools. Data can be collected using the 'collect'command. All data can be converted into performance metrics computed against functions, callers and callees of any functions, and against source and disassembly of the target program. The 'er_print' command is used to get an ASCII output of the performance metrics obtained from the 'collect' command. Three types of function-level metrics can be computed using the performance analysis tools: Exclusive metrics: are calculated from events which occur inside the function itself: they exclude metrics coming from calls to other functions. Inclusive metrics: are collected from events which occur inside the function and any functions it calls: they include metrics coming from calls to other functions Attributed
metrics:are the parts of the inclusive metric of the selected
function that are due to calls from a caller or calls to a callee.
Exclusive user CPU time is the amount of time spent in the function itself, in seconds Inclusive user CPU time is the amount of
time spent in the function itself and any functions it calls, in seconds
Callers-callees data: Prints the callers-callees panel for each of the functions, in the order in which they are sorted. The selected (middle) function is marked with an asterisk. The callers of the selected function are shown above. The functions which the selected function calls are listed below. Leaks data: The ?Leaks? report shows what
memory has been leaked while the program was running.
4.2 Quantify data Functions list: Displays the list of function calls sorted by percentage of '.root' Exports file: Is the ASCII version of the quantify data. Elaborates on all the callers of a particular function, the number of times the function was called, propagated time, the function descendant time and many more metrics. Annotated source: Presents a line by line performance data using the functions source code. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
**************************Disclaimer************************************************** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ****************************************************************************************