Go pprof Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 5: Line 5:
=Profile=
=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|goroutine]], [[#heap|heap]], [[#threadcreate|threadcreate]], [[#block|block]], [[#mutex|mutex]] and [[#profile|profile]], which is the short for "CPU profile".
A '''profile''' is a collection of stack traces showing the call sequences that led to instances of a particular event, such as allocation, plus some additional metadata. 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|goroutine]], [[#heap|heap]], [[#threadcreate|threadcreate]], [[#block|block]], [[#mutex|mutex]] and [[#profile|profile]], which is the short for "CPU profile".


<code>[[Go_pprof_Operations#go_tool_pprof|go tool pprof]]</code> is the tool that can be used to analyze these profiles.
<code>[[Go_pprof_Operations#go_tool_pprof|go tool pprof]]</code> is the tool that can be used to analyze these profiles.

Revision as of 04:12, 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, plus some additional metadata. 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, heap, threadcreate, block, mutex and profile, which is the short for "CPU profile".

go tool pprof is the tool that can be used to analyze these 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:

  • running
  • chan 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

http://localhost:8080/debug/pprof/trace?seconds=5

produces a trace, not a profile. The data collected as such can be viewed with go tool trace.