New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: Make docs more accurate for the contention-profiling flag #114490
*: Make docs more accurate for the contention-profiling flag #114490
Conversation
The --contention-profiling flag enables block profiling by calling SetBlockProfileRate(). It, however does not call SetMutexProfileFraction which enables mutex profiling. Mutex profiling gives us information about lock contention whereas block profiling on the other hand gives us information on gorotuines being blocked on sync primitives. Updating the docs to "block profiling" in order to make it more accurate. Eventhough a block profile may reflect contention points on locks to some extent, it also talks about other sources where goroutines may be blocked. Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
/priority backlog |
/priority important-longterm |
/assign @MikeSpreitzer |
/assign @ahg-g @derekwaynecarr @sttts |
/lgtm |
LGTM label has been added. Git tree hash: f418a60fc20469945dbff302dd5d093a4beeb68b
|
/approve a simple but important docs change |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, MadhavJivrajani, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@dims is this something that is usually cherry-picked? |
Created cherry-picks:
Since these docs are surfaced to the users. |
@MadhavJivrajani usually No! |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The
--contention-profiling
flag enables block profiling by calling SetBlockProfileRate(). It, however does not call SetMutexProfileFraction which enables mutex profiling.Mutex profiling gives us information about lock contention whereas block profiling on the other hand gives us information on gorotuines being blocked on sync primitives.
Updating the docs to "block profiling" in order to make it more accurate. Eventhough a block profile may reflect contention points on locks to some extent, it also talks about other sources where goroutines may be blocked.
Calling it lock contention may cause confusion, one such instance is kubernetes/perf-tests#2215
Which issue(s) this PR fixes:
Fixes # NA
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig docs