Hi,
is it by design, or is there a better way to show me real figures with Hit Count, by real I don't mean that your numbers are wrong.
However, in the 'All Methods Grid' I can sort by Hit Count, it shows that largest hit count in my app is
136,290 (shown in red) - which is the ctor method of a key class.... I am happy with that...
It then shows
19,817 (shown in red) hits to the ctor method, this time the pricelist class, again, number wise - all ok.
The problem is that inside the pricelist class there is a predicate that has been created _bySortOrder that according to the hit count in the source window has been call
253,232 (shown in green) times.
Private Function _bySortOrder(ByVal x As ProductBasics, ByVal y As ProductBasics) As Integer
Return x.SortOrder.CompareTo(y.SortOrder)
End Function
Now the actual number of calls I don't have a problem with, and it certainly highlights a performance issue that I can work on (which is way we need ANTS anyway!!!)
I also understand that the colours represented are based on time / time with children. I also understand that the predicate is very fast.
my question is ... why does this method not get shown in the summary section with it's large hit count, I don't want to go searching for these bottlenecks when you have the information already.
Hope that makes sense

Paul.
is it by design, or is there a better way to show me real figures with Hit Count, by real I don't mean that your numbers are wrong.
However, in the 'All Methods Grid' I can sort by Hit Count, it shows that largest hit count in my app is 136,290 (shown in red) - which is the ctor method of a key class.... I am happy with that...
It then shows 19,817 (shown in red) hits to the ctor method, this time the pricelist class, again, number wise - all ok.
The problem is that inside the pricelist class there is a predicate that has been created _bySortOrder that according to the hit count in the source window has been call 253,232 (shown in green) times.
Now the actual number of calls I don't have a problem with, and it certainly highlights a performance issue that I can work on (which is way we need ANTS anyway!!!)
I also understand that the colours represented are based on time / time with children. I also understand that the predicate is very fast.
my question is ... why does this method not get shown in the summary section with it's large hit count, I don't want to go searching for these bottlenecks when you have the information already.
Hope that makes sense
Paul.