- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- Capturing snapshots
- Solving performance problems
- CPU profiling
- 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
- Time measurement (CPU time, wall time)
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler API
- Profiler HTTP API
- Command line tool to control profiling
Probes: monitor higher level events
Probes collect information about different events in the profiled application:
- Web pages (ASP.NET request processing)
- Database activity (connections, transactions, SQL statement execution)
- Socket I/O (socket reads and writes)
- File I/O (file reads and writes)
- Class loading and unloading events (load/unload time stamp, class name, module, application domain, and, if applicable, initiating thread and stack trace)
How to enable probes
You can choose whether to enable probes when starting application with the profiler. If probes are enabled, probe activity mode can be changed in runtime. Read more...
What kind of information is recorded for each event?
- Where it happened: stack trace, thread
- When it happened
- If applicable, event duration and consumed CPU time
- Event-specific numerical or text information. For example, this can be the number of bytes written to a file, or the URL of accessed web page.
How to access the recorded information?
Probes UI provides rich set of tools to analyze the gathered information, or to export it for external processing.