Bump java-profiler (ddprof) to 1.47.0#12055
Conversation
Required to continue work on the all-native profiler context bridge (#11899).
|
🎯 Code Coverage (details) 🔗 Commit SHA: 3808810 | Docs | Datadog PR Page | Give us feedback! |
There was a problem hiding this comment.
More details
The dependency bump is internally consistent: the version catalog and all locked ddprof configurations resolve to 1.47.0, while profiler API call sites are unchanged. Local Gradle execution was blocked before project evaluation because the pinned distribution could not be downloaded and the installed Gradle requires an unavailable Java 25 toolchain.
🤖 Datadog Autotest · Commit 9f389fe · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
The ddprof 1.47.0 native library growth pushed the shadow jar past the previous budget; raise it to unblock the verifyAgentJarContents check.
🟢 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.
The expected merge time in
|
What Does This Do
Bump java-profiler (ddprof) from 1.46.0 to 1.47.0 in
gradle/libs.versions.toml, and regeneratedd-java-agent/ddprof-lib/gradle.lockfileaccordingly. Also raisemetadata/agent-jar-checks.properties'sjar.size.budget, since the updated native library grew the shadow jar past the previous limit.Motivation
Brings in the all-native OTEL context write API (Phase 1), needed to continue #11899.
Additional Notes
Noticeable changes
See full release notes
Jar size budget
The shadow jar grew past the previous
jar.size.budget, so this PR raises it (~33.02 MiB). The growth is almost entirely from the new all-native context API added in java-profiler#631:ddprof.jargained a newContextValueCacheclass and an expandedJavaProfiler(+16.7 KB), and the native libraries gained the new JNI entry points injavaApi.cpp(+~4 KB each on x64/arm64).This is expected to be temporary. Per java-profiler's migration design note (§7, "expand → migrate → contract"), this release is the additive "expand" phase — the new API lands alongside the old
DirectByteBuffer/CarrierThreadLocal-based context path. Once dd-trace-java fully migrates to the native API (#11899) and java-profiler ships its "contract" release, the oldOtelContextStorage/BufferWriter*/most ofThreadContext(~1,200 lines, Java-side only) get deleted, which should shrinkddprof.jaragain — likely below the pre-1.47.0 baseline. The native.sogrowth from this release is expected to stay, though, since it's the new production code path rather than scaffolding, and the old DBB path's native footprint was minimal to begin with.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 issue/merge.🤖 Generated with Claude Code