Go pprof Concepts: Difference between revisions
(→mutex) |
|||
| Line 31: | Line 31: | ||
==<tt>mutex</tt>== | ==<tt>mutex</tt>== | ||
The profile contains stack traces of holders of contended mutexes. | The profile contains stack traces of holders of contended mutexes. | ||
==<tt>profile</tt>== | |||
This profile contains the CPU profile. | |||
=<tt>trace</tt>= | |||
This produces a trace, not a profile. | |||
Revision as of 04:06, 16 November 2024
External
Internal
Overview
Profile
A profile is a collection of stack traces showing the call sequences that led to instances of a particular event, such as allocation. Packages can create and maintain their own profiles. The most common use is for tracking resources that must be explicitly closed, such as files or network connections.
Each profile has a unique name.
There are a few predefined profiles:
goroutine
The profile contains the stack traces of all current goroutines. This is how you can pull it from the process with curl.
The goroutines can be in one of the following states:
runningchan receive[, x minutes]syscall[, x minutes]select[, x minutes]IO wait[, x minutes]sync.Cond.Wait[, x minutes]semacquire[, x minutes]
heap
The profile contains a sampling of all heap allocation.
threadcreate
The profile contains stack traces that led to the creation of new OS threads.
block
The profile contains stack traces that led to blocking on synchronization primitives.
mutex
The profile contains stack traces of holders of contended mutexes.
profile
This profile contains the CPU profile.
trace
This produces a trace, not a profile.