Any Advantages to Profiling IIS Appliction vs. Attach to .Net Process

I have an IIS Web Application that I need to profile.  The Application is running on a pre-production environment.  Currently, I installed dotTrace on the actuall server and I'm using Profile IIS Application which requires me to restart IIS and tends to consume a lot of CPU especially when using Tracing mode.  Are there any advantages or disadvantages to either using the Attach to .Net Process instead of IIS Applicatoin or using the Remote Agent and running the Profiler from a remote machine?

1 comment

Hello Mark,

If you want to use the 'Attach to Process' feature, please pay attention that only one profiling method (sampling) will be available because of .NET Framework restrictions. If you need line-by-line and tracing profiling methods, please start your application under dotTrace.

Kind regards,


Please sign in to leave a comment.