Avoid Netty queue-timing metadata reads before JFR is ready - #12558
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
More details
The readiness guards stop metadata reads before JFR is ready. They keep trace propagation active and support delayed profiling startup.
🤖 Datadog Autotest · Commit c80ba43 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
|
/merge |
|
View all feedbacks in Devflow UI.
Progress updates will be sent here directly.
merge method 'merge' is not allowed for this repository. Supported methods are: [squash]
The following PRs won't be merged. The current stack is: |
There was a problem hiding this comment.
More details
The readiness guards preserve trace propagation. They prevent queue metadata reads before JFR initialization.
🤖 Datadog Autotest · Commit c80ba43 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Build pipeline has failing jobs for 3a8b393:
What to do next?
DetailsSince those jobs are not marked as being allowed to fail, the pipeline will most likely fail. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
81d4706
into
master
What Does This Do
Reuse
QueueTimerHelper.isReady()from the preceding PR (#12550) to skip unnecessary work in Netty’s ordinary, delayed and scheduled queue-timing advice.Before JFR is ready, this avoids context-store lookups, queue-size reads and scheduler metadata collection. The readiness check remains dynamic to support delayed profiling startup.
Motivation
Additional Notes
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: [PROJ-IDENT]