Activity overview
Latest activity by asthomas
Thank you, Jessica. I have another suggestion as well:
Suggestion #3:
I am frequently misled by the CPU percentage numbers in Ants because Ants does not report on CPU used in unmanaged threads. The problem is that I can select a region and produce a call tree that suggests that a certain function is using 50% of the CPU. That is true, for those threads that Ants is profiling, but in reality that represents 50% of the 4% that Ants is actually reporting on. The rest of the CPU (96%) is in unmanaged code. In order to try to determine whether I'm looking at that kind of situation I'm constantly flipping between "Wall Time" and "CPU Time" reports. When I do that, the call tree is re-sorted and I lose track of what I was studying.
Consequently, I would like to suggest that you provide an option to put columns for *both* wall time and CPU time in all of the tables. The selection of wall or CPU time would determine how the table is sorted, but both would be displayed. / comments
Thank you, Jessica. I have another suggestion as well:
Suggestion #3:
I am frequently misled by the CPU percentage numbers in Ants because Ants does not report on CPU used in unmanaged threads. T...
Suggestions for enhancement
I'm working with an application that has many threads, about 60 in all. Some are running managed code and some are running unmanaged code. Some of the managed threads are worker threads that get ...
Wrong CPU attribution in Monitor, Mutex and Semaphore?
My program makes use of C#'s lock, which is a wrapper on the Monitor object.
lock (myObject)
{
// do something
}
When I run my program with Ants, the Monitor.Enter and Monitor.Release calls ap...
I would like to second this. I am evaluating the RedGate profiler against the VS2010 profiler for Silverlight. VS2010 has line-level profiling and it was able to point to, quite literally, 2 lines (simple property access) that were consuming 20% of the run time on one of our controls. Simple code refactoring cleared it right up. The RedGate profiler would not have helped here.
My gut feeling is that Silverlight performance is very sensitive to seemingly trivial calls. Line level profiling is absolutely essential. / comments
I would like to second this. I am evaluating the RedGate profiler against the VS2010 profiler for Silverlight. VS2010 has line-level profiling and it was able to point to, quite literally, 2 line...