Backport of CLI: remove redundant allocs profile from operator debug into release/1.7.x
#20226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-nomad-core
force-pushed
the
backport/b-operator-debug-memory-profile/brightly-gorgeous-crow
branch
from
700c9c9 to
a8e98e6
Compare
tgross
approved these changes
Mar 26, 2024
tgross
deleted the
backport/b-operator-debug-memory-profile/brightly-gorgeous-crow
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #20219 to be assessed for backporting due to the inclusion of the label backport/1.7.x.
The below text is copied from the body of the original PR.
The pprof
allocsprofile is identical to theheapprofile, just with a different default view. Collecting only one of the two is sufficient to view all ofalloc_objects,alloc_space,inuse_objects, andinuse_space, and collecting only one means that both views will be of the same point in time.Also improve the docstrings on the goroutine profiles explaining what's in each so that it's clear why we might want all of debug=0, debug=1, and debug=2.
Overview of commits