fix(llmobs): fix propagation memory usage [backport 2.9] #9392
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 be9936b from #9387 to 2.9.
This PR is a follow up of #9152, and attempts to minimize any added memory overhead by moving the
llmobs
utility import to inside the conditional check thatLLMObs
is enabled.By importing inside the
ddtrace.llmobs.
directory we are implicitly running theddtrace.llmobs.__init__.py
code, which involves instantiating aLLMObs
instance. This is likely the largest culprit of the memory overhead.Moving the import to only happening if LLMObs is enabled should avoid that added overhead, given that LLMObs is only running in a select few customer applications at the moment.
Checklist
changelog/no-changelog
is set@DataDog/apm-tees
.Reviewer Checklist