- Running applications with the profiler
- Profile local applications
- Profile .NET executable
- Profile IIS application
- Profile Silverlight application
- Profile all .NET processes that will start
- Manually enable profiling of local applications
- Local profiling troubleshooting
- Attaching agent to running application
- Profile remote applications
- Startup options
- Profiling overhead: how to reduce or avoid
- Connect to profiled application
- Capturing snapshots
- Solving performance problems
- CPU profiling
- Threads
- Memory profiling
- Garbage collection
- Exception profiling
- Probes: monitor higher level events
- Performance charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- Integration with Microsoft Visual Studio
- Time measurement (CPU time, wall time)
- Filters
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler API
- Command line tool to control profiling
Profile IIS application
To profile IIS, run the profiler from Windows Start menu as administrator (privileges are needed to re-start IIS service):
Alternatively, change the profiler shortcut properties to always run the profiler as administrator:
Use Profile IIS application... action on Welcome screen or in "Profile" menu.
The window will appear:
Press Start IIS Profiling to re-start IIS service. You can alter advanced profiling options if necessary.
To profile your ASP.NET application open it in a browser and connect to it from "Monitor Applications" list on Welcome screen. IIS will create .NET runtime on first web request, until this moment your application will not appear in "Monitor Applications" list.