woodtime / webgrind

Automatically exported from code.google.com/p/webgrind
Other
0 stars 0 forks source link

Total Inclusive Costs greater than total execution time on large cachegrind files #54

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Load a magento profiling file (see attachment)
2. compare total inclusive costs (3732ms) with the total execution time (1659ms)
3. compare values to kcachegrind - Values <1000 are good, values > 1000 not.

What is the expected output? What do you see instead?
The expected output would be max(total_inclusive_cost) <= total execution time
and the same as in kcachegrind

What version of the product are you using? On what operating system?
v. 1.0

Please provide any additional information below.
I'm profiling a magento shop system. The profiling was always good when having 
a total execution time <1000 ms. Over 1000 ms the total inclusive costs are 
more than 100% of the total execution time, which is not correct. Comparing the 
values to the magento profiler and the loaded cachegrind file in kcachegrind 
shows, that the values in webgrind are not the same and not correct.
The File of the profiling is attached.

Original issue reported on code.google.com by happycap...@gmail.com on 10 Aug 2010 at 8:27

Attachments:

GoogleCodeExporter commented 8 years ago
The total inclusive costs cannot be summed as that figure includes the function 
call and any further calls that method may invoke. 

Original comment by gugakf...@gmail.com on 28 Sep 2010 at 12:30