In my application, which is a combination of C# and P/Invoke calls to a custom C++ DLL, dotTrace is showing very silly numbers for some calls. eg: 71,216,970,000.00% 6,261,325,000,000.0ms
See screen shot for example.
This makes determining which calls are actually consuming the most time very difficult.
It would be nice if there was some way of getting rid of this junk data or having dotTrace record accurate data.
Description
In my application, which is a combination of C# and P/Invoke calls to a custom C++ DLL, dotTrace is showing very silly numbers for some calls. eg: 71,216,970,000.00% 6,261,325,000,000.0ms
See screen shot for example.
This makes determining which calls are actually consuming the most time very difficult.
It would be nice if there was some way of getting rid of this junk data or having dotTrace record accurate data.
George Udov - 29 May 07 12:52 Dear Oliver,
1) Which CPU do you have? Is it AMD-X2 or Core-Duo?
2) Are you able to reproduce these problems on any profilee application or only on special one?
AMD Athlon 64 X2 Dual Core. My trial license to dotTrace has expired so I can't test any other apps sorry. Other profilers (eg YourKit) don't seem to have this problem.
Oliver Jones - 30 May 07 05:45 AMD Athlon 64 X2 Dual Core. My trial license to dotTrace has expired so I can't test any other apps sorry. Other profilers (eg YourKit) don't seem to have this problem.
1) Which CPU do you have? Is it AMD-X2 or Core-Duo?
2) Are you able to reproduce these problems on any profilee application or only on special one?