Skip to content
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

Adjustments to the 2020 description of wallclock profiling for the JVM #27493

Merged

Conversation

MattAlp
Copy link
Contributor

@MattAlp MattAlp commented Feb 6, 2025

What does this PR do? What is the motivation?

This modifies the original Java profile types documentation from 2020 to more accurately reflect the wallclock profiling functionality, based on some internal discussions with sales & support engineering recently.

Merge instructions

Merge readiness:

  • Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

@MattAlp MattAlp requested a review from a team as a code owner February 6, 2025 20:19
Copy link
Contributor

github-actions bot commented Feb 6, 2025

Preview links (active after the build_preview check completes)

Modified Files

@drichards-87
Copy link
Contributor

/merge

@dd-devflow
Copy link

dd-devflow bot commented Feb 6, 2025

Devflow running: /merge

View all feedbacks in Devflow UI.


2025-02-06 21:14:17 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in master is 7m.


2025-02-06 21:21:15 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit adf9cee into master Feb 6, 2025
17 of 21 checks passed
@dd-mergequeue dd-mergequeue bot deleted the mattalp/correct-misleading-wallclock-explanation branch February 6, 2025 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants