Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Understand profiling types and their uses in Pyroscope
Profiling is an essential tool for understanding and optimizing application performance. In Pyroscope, various profiling types allow for an in-depth analysis of different aspects of your application. This guide explores these types and explain their impact on your program.
Profiling types
In Pyroscope, profiling types refer to different dimensions of application performance analysis, focusing on specific aspects like CPU usage, memory allocation, or thread synchronization.
Pyroscope supports these profile types:
- CPU (CPU time, wall time)
- Memory (allocation objects, allocation space, heap)
- In use objects and in-use space
- Goroutines
- Mutex count and duration
- Block count and duration
- Lock count and duration
- Exceptions
Refer to the Profile types tables for information on supported profile types based on instrumentation method.
For information on auto-instrumentation and supported language SDKs, refer to Configure the client.