Bug 51498 - Count column not visible
Summary: Count column not visible
Status: Tracked in Related Links
Alias: None
Product: Profiler
Classification: Xamarin
Component: Mac ()
Version: 1.0.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: 15.6
Assignee: Rodrigo Moya
URL:
Depends on:
Blocks:
 
Reported: 2017-01-13 08:26 UTC by Christophe Oosterlynck
Modified: 2019-03-07 23:02 UTC (History)
7 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
No count column visible (154.01 KB, image/png)
2017-01-13 08:26 UTC, Christophe Oosterlynck
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 51498 on Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:
Status:
Tracked in Related Links

Description Christophe Oosterlynck 2017-01-13 08:26:52 UTC
Created attachment 19318 [details]
No count column visible

There used to be a "Count" column in the Xamarin Profiler Mac UI (Time Profiler). It has suddenly disappeared. Now I only have 
* Running Time
* Self
* Symbol Name

I can't remember doing anything that could have triggered this (no updates or anything of that kind).
Comment 1 Rodrigo Moya 2017-01-13 14:18:59 UTC
This was because we used method enter/leave before for getting timing information, which hits hard the performance of the app being profiled and is not as accurate as what we use now, sampling. And, when using sampling, we don't know how many times a method was called, like we used to get when using method enter/leave.

We might want to add an option to allow method enter/leave instead of sampling if the user chooses to.
Comment 2 Christophe Oosterlynck 2017-01-17 13:29:21 UTC
An option to use enter/leave functionality instead of sampling would indeed be nice. The amount of times a method was called seems very important to me when trying to understand a profiling result. When a lot of time is spent in 1 method it could be because the method is doing some heavy stuff or it is just being called a lot and the problem is elsewhere.
Comment 3 Rodrigo Moya 2017-03-06 21:34:54 UTC
Or maybe, when using sampling, we could display the number of samples for that method, instead of the count call. I think this might be better than resurrecting method enter/leave, which we don't want to offer to the user, as it degrades performance so much, than profiling becomes useless
Comment 4 Dominic N [MSFT] 2017-09-22 19:19:23 UTC
Moving to future milestone.