我还要补充一点，dotTrace区分内存和性能跟踪会话的能力绝对是无价的(ANTS可能也有内存差异特性，但我没有看到性能差异)。

能够在bug修复或增强之前和之后运行一个分析会话，然后比较结果是非常有价值的，特别是对于一个庞大的遗留的。net应用程序(就像我的情况)，性能从来都不是优先考虑的，而且查找瓶颈可能非常乏味。执行前后差异可以查看每个方法的调用计数变化和每个方法的持续时间变化。

This is helpful not only during code changes, but also if you have an application that uses a different database, say, for each client/customer. If one customer complains of slowness, you can run a profiling session using their database and compare the results with a "fast" database to determine which operations are contributing to the slowness. Of course there are many database-side performance tools, but sometimes I really helps to see the performance metrics from the application side (since that's closer to what the user's actually seeing).

总结:dotTrace工作得很好，差异是无价的。

如果许可是一个问题，您可以尝试WINDBG进行内存分析

我自己还没试过，但也许dotTrace?他们的ReSharper应用程序当然是一个很好的应用程序。也许dotTrace也是:)

我以前跟红门的侧写师合作过。帮我完成了任务。

我还要补充一点，dotTrace区分内存和性能跟踪会话的能力绝对是无价的(ANTS可能也有内存差异特性，但我没有看到性能差异)。

能够在bug修复或增强之前和之后运行一个分析会话，然后比较结果是非常有价值的，特别是对于一个庞大的遗留的。net应用程序(就像我的情况)，性能从来都不是优先考虑的，而且查找瓶颈可能非常乏味。执行前后差异可以查看每个方法的调用计数变化和每个方法的持续时间变化。

This is helpful not only during code changes, but also if you have an application that uses a different database, say, for each client/customer. If one customer complains of slowness, you can run a profiling session using their database and compare the results with a "fast" database to determine which operations are contributing to the slowness. Of course there are many database-side performance tools, but sometimes I really helps to see the performance metrics from the application side (since that's closer to what the user's actually seeing).

总结:dotTrace工作得很好，差异是无价的。

如果你是ASP。你可以尝试MVCMiniProfiler (http://benjii.me/2011/07/using-the-mvc-mini-profiler-with-entity-framework/)