Any decent C# profilers out there? [closed]
https://stackoverflow.com/questions/10644
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianQuestion
I need a C# profiler.
Although I'm not averse to paying for one, something which is free or at least with a trial version would be ideal since it takes time to raise a purchase order.
Any recommendations?
Solution
You can try the following:
- nprof (free but kinda old)
- ProfileSharp (open source)
- .Net Memory Profiler (really good for memory leaks, there's a trial version)
Edit: Nprof has been replaced with SlimTune and works with .Net 4.0 applications
OTHER TIPS
I used Ants profiler on a large c# project a year and a half ago. It really performed very nicely for what it cost, and even outperformed a few of the more expensive competitors.
It calculates cost on with almost a line by line resolution.
The EQATEC profiler is very good and is completely free. It's easy to setup and use, and doesn't seem to add too much of an overhead to the application. I've just started using it today and have already found a couple of bottlenecks I wouldn't have spotted otherwise.
I maintain a comprehensive list of profilers for .NET on SharpToolbox.com.
You'll find there the tools suggested here and more, each with a short description of what it proposes.
It's interesting that no-one mentions that there's one in the higher-end versions of Visual Studio - I've always found that to be good enough for execution profiling. For memory profiling I use Memory Profiler which has already been mentioned, but isn't what I would generally describe as 'a profiler'.
What kind of profiling were you trying to do?
We use Ants profiler where I work. It gives very detailed information in a simple manner.
We use .NET Memory Profiler. Its kinda ugly but very useful for finding dangling references.
I originally tried Red Gate's ANTS profiler which is very sexy, but from a memory leak point of view it sucks for the following reasons:
1) Its ridiculously slow. It was taking half an hour to get the application into a state to start recording (takes 20 seconds without red-gate).
2) Red Gate needs to run its own tool on its own tool. It was using 900MB of memory by the time I finished two snapshots! It then crashed :(
However the timing component of Red Gate ANTS was impressive. Just don't bother with the memory profiler, unless you are dealing with a trivial (small footprint) application.
I have used AQtime and it has never let me down. I am sure there is a trial version.
I'll second red gate's ANTS profiler. I've used it to track down some really troubling performance issues and it was dead simple to use (low learning curve) and presented nice, detailed data in a way that was easy to understand. The price tag is worth it, but it isn't free ...
Patrick Smacchia's awesome NDepend is excellent for providing static analysis.
I would thoroughly recommend NDepend for static analysis, but just be warned that you'll probably need to put aside a day or two to actually analyse the truckload of information that it provides as well as work out what all the stats actually mean in terms of your code.
I have had good luck with the .NET memory profiler
EQATEC profiler did the job here.
The current release of SharpDevelop (3.1.1) has a nice integrated profiler. It's quite fast, and integrates very well into the SharpDevelop IDE and its NUnit runner. Results are displayed in a flexible Tree/List style (use LINQ to create your own selection). Doublecliking the displayed method jumps directly into the source code.
Currently don't use them, a buddy of mine raves about Ants profiler. I know its a for-pay product not sure how expensive. If you happen to staff an MVP you might be able to leverage that to get a license for free.
AQTime (both perf and memory) or ANTS (v4 performance profiler or v5 beta memory profiler) here.
I found the .NET Memory Profiler yesterday, and I must say that I'm very impressed by it.
I'm going to order my license today.
Although not very good to profile memory usage, the profiler included in some versions of Visual Studio does a very good job of profiling execution speed.
What's your objective?
Is it your objective to locate specific statements and get a rough idea of what they are contributing to your total execution time, so you can find ways to do them differently?
