Early access program feedback
Thanks for stopping to share your feedback on the ANTS Performance Profiler early access program, from Red Gate. The latest build makes ANTS Performance Profiler the only .NET profiler to show how your .NET code generates database calls, whether to SQL or Oracle servers. We need your feedback to make ANTS Performance Profiler better – let us know about features we’re missing, problems you’re encountering, or just how you feel about the tool.
-
WCF Memory
Will be great if Ants Profiler could monitor and verify the performance to communicate between client and server application, for e.g. in WCF, how much data is transferred, in what time, network speed.
3 votes -
Improve processor display
Sometimes is very important to see every core of the processor what operation makes, and to see in a multithread application what thread do what.
If you have a application that uses 4 cores, for eg. the application can use very much the first core and the other 3 to make only simple tasks.6 votes -
Be able to debug an IIS application with .net framework 4 (NOT .Net 2)
I am sure i tried ants profiler a year or so ago and this wasnt an issue. However I have tried version 6.3, 7.0, and the early access builds and all of them demonstrate the fact that when selecting the base options, and to restart iis and reuse the port, the application pool ants profiler creates is in .net 2, which is no good to anyone. We can still "attach to w3wp.exe" to get some information, but it is at the level of methods, whereas we are very much interested in line level timings.
This is the exact same issue: …6 votes -
4 votes
- Don't see your idea?