- Running applications with the profiler
- Profile local applications
- Profile local standalone application
- Profile local 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 telemetry
- 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 local IIS application
The following describes profiling of local IIS applications.
Read about profiling other types of local applications here.
Read about profiling remote applications here.
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:
When the profiler starts, choose corresponding item on the Welcome screen:
The dialog window will appear.
Choose profiling options, then press Profile to re-start IIS service with the profiler.
The profiler will automatically connect to the profiled application as soon as the application receives first request, e.g. as soon as you open its page in your browser.