Performance data for Theme capplet

[muktha <muktha narayan wipro com>]

Hi All,
Please find attached the performance report for Theme properties
capplet.

The performance data was collected using the forte profiling tools and
Rational quantify
tool.

The report highlights only the top five expensive functions. Please get
back to us in
case you need additional information / data.

Thanks 'n Regards
Anand & Muktha

Title:

Gnome Theme Preferences Performance Data Summary Report
(version 1.0)

1. Component Summary
 
 

Name of the Component	Gnome Theme Preferences
QA Contact	muktha narayan wipro com, anand subra wipro com
Test Setup	Config Parameter		Forte Setup		Quantify Setup
	Hardware Details		Sparc Ultra 10, 333 Mhz, 1 CPU		Sparc Enterprise 250, 200 Mhz, 2 CPU
	Memory		128 MB		1024 MB
	Operating system		Solaris 9, 64 Bit		Solaris 8, 64 Bit
Build Details	Source Code Location			CVS
	CVS Branch			gnome-2-0
	CVS Checkout Time Stamp			Forte	Quantify
				Wed Oct 16 10:25:13 2002	Thu Oct 03 01:29:16 2002
	Compiler (Version Infomation)			Forte
Performance Utilities Used	Quantify			qv
	Forte			collect  er_print
	Other Tools/Scripts			-
Total. No. Of tests Run	1

 

2. Brief Description of Tests Done to Collect Performance Data
 
 

Test No.	Test synopsis
Theme_01	Invoked Gnome Theme properties capplet from the command prompt, changed the theme to 'HighContrastLargePrintInverse' and then reverted to 'Default' theme.

 

3. Data

2.1 Test: Theme_01

As per the quantify data collected, the first 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 800KB memory leak, when the theme was changed and reverted back.
 

Function Name	Caller	Callees	Quantify Details	Forte Details
lookup_type_node_I	type_descriptive_name_I  g_type_interface_add_prerequisite type_iface_vtable_init_Wm       g_type_register_fundamental      g_type_add_interface_static      g_type_depth    lookup_type_node_I check_add_interface_L g_type_qname    lookup_type_node_I g_type_set_qdata type_data_make_W g_type_get_qdata check_derivation_I g_type_register_static g_type_class_peek_parent check_type_info_I        g_type_interfaces        g_type_test_flags        type_class_init_Wm       type_node_fundamental_info_I     g_type_name      g_type_free_instance     g_type_class_peek        g_type_check_class_is_a  g_type_class_unref       g_type_check_class_cast  g_type_class_ref         g_type_create_instance   g_type_fundamental       g_type_interface_peek    g_type_check_instance   g_type_parent    g_type_is_a  g_type_value_table_peek  type_check_is_value_type_U   g_type_check_instance_cast     g_type_check_instance_is_a	None	Called: 710424 times Function time: 25183031 cycles ( 5.94% of .root.) Function+descendants time: 25183031 cycles ( 5.94% of .root.)	Exclusive time: 0.120 secs Inclusive time: 0.120 secs Attributed time: 0.120 secs
type_node_check_conformities_UorL	type_node_is_a_L type_node_conforms_to_U	g_static_rw_lock_reader_unlock type_lookup_iface_entry_L	Called: 256737 times Function time: 21402772 cycles ( 5.05% of .root.) Function+descendants time: 24026096 cycles ( 5.67% of .root.)	Exclusive time: 0.070 secs Inclusive time: 0.090 secs Attributed time: 0.070 secs
scale_line	pixops_process	None	Called: 636 times Function time: 20234992 cycles ( 4.78% of .root.) Function+descendants time: 20234992 cycles ( 4.78% of .root.)	Exclusive time: 0.070 secs Inclusive time: 0.070 secs Attributed time: 0.070 secs
g_type_check_instance_cast	gdk_window_impl_x11_get_colormap _gdk_x11_gc_flush gdk_x11_draw_segments gtk_list_store_get_value gtk_object_get_data_by_id gtk_scrolled_window_size_request gtk_signal_emit gtk_tree_model_get_valist gtk_widget_freeze_child_notify gtk_widget_propagate_hierarchy_changed_recurse pango_x_fontmap_cache_add pango_x_make_matching_xlfd	type_node_conforms_to_U lookup_type_node_I	Called: 112432 times Function time: 14840949 cycles ( 3.50% of .root.) Function+descendants time: 38095281 cycles ( 8.99% of .root.)	Exclusive time: 0.050 secs Inclusive time: 0.130 secs Attributed time: 0.050 secs
g_type_check_instance_is_a	g_object_ref g_object_unref g_param_spec_get_qdata gdk_draw_line _gtk_style_peek_property_value g_param_spec_unref gdk_draw_layout gdk_x11_gc_set_values gtk_tree_model_get_value gtk_widget_region_intersect gtk_widget_unref	type_node_conforms_to_U lookup_type_node_I	Called: 116350 times Function time: 12797178 cycles ( 3.02% of .root.) Function+descendants time: 38336302 cycles (9.05% of .root.)	Exclusive time: 0.050 secs Inclusive time: 0.170 secs Attributed time: 0.050 secs

 

3.1.1 Forte Collect Data
 
 

Sl. No.	Data Collected	Pointer to Data
1	er_print callers-callees data	Gzipped Text File (29 KB)
2	er_print leaks data (for the top 500 leaks) [1]	Gzipped Text File (39 KB)

 

3.1.2 Quantify Data
 
 

Sl. No.	Data description	Pointer to Data
1	Functions list	Gzipped Text File (30 KB)
2	Export File	Gzipped Text File (249 KB)
3	Annotated source files for the top five expensive functions	- lookup_type_node_I (44 KB) - type_node_check_conformities_UorL (44 KB) - scale_line (9 KB) - g_type_check_instance_cast (44 KB) - g_type_check_instance_is_a (44 KB)

[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.