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

fix(llmobs): fix propagation memory usage [backport 2.9] #9392

Merged
merged 2 commits into from
May 28, 2024

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented May 24, 2024

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 that LLMObs is enabled.

By importing inside the ddtrace.llmobs. directory we are implicitly running the ddtrace.llmobs.__init__.py code, which involves instantiating a LLMObs 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

  • Change(s) are motivated and described in the PR description
  • Testing strategy is described if automated tests are not included in the PR
  • Risks are described (performance impact, potential for breakage, maintainability)
  • Change is maintainable (easy to change, telemetry, documentation)
  • Library release note guidelines are followed or label changelog/no-changelog is set
  • Documentation is included (in-code, generated user docs, public corp docs)
  • Backport labels are set (if applicable)
  • If this PR changes the public interface, I've notified @DataDog/apm-tees.

Reviewer Checklist

  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Description motivates each change
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Change is maintainable (easy to change, telemetry, documentation)
  • Release note makes sense to a user of the library
  • Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance policy

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 that `LLMObs` is enabled.

By importing inside the `ddtrace.llmobs.` directory we are implicitly
running the `ddtrace.llmobs.__init__.py` code, which involves
instantiating a `LLMObs` 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

- [x] Change(s) are motivated and described in the PR description
- [x] Testing strategy is described if automated tests are not included
in the PR
- [x] Risks are described (performance impact, potential for breakage,
maintainability)
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed or label `changelog/no-changelog` is set
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/))
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))
- [x] If this PR changes the public interface, I've notified
`@DataDog/apm-tees`.

## Reviewer Checklist

- [x] Title is accurate
- [x] All changes are related to the pull request's stated goal
- [x] Description motivates each change
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- [x] Testing strategy adequately addresses listed risks
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x] Release note makes sense to a user of the library
- [x] Author has acknowledged and discussed the performance implications
of this PR as reported in the benchmarks PR comment
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

(cherry picked from commit be9936b)
@github-actions github-actions bot added the changelog/no-changelog A changelog entry is not required for this PR. label May 24, 2024
@github-actions github-actions bot requested a review from a team as a code owner May 24, 2024 23:08
@github-actions github-actions bot requested a review from erikayasuda May 24, 2024 23:08
@Yun-Kim Yun-Kim added changelog/no-changelog A changelog entry is not required for this PR. and removed changelog/no-changelog A changelog entry is not required for this PR. labels May 24, 2024
@Yun-Kim Yun-Kim enabled auto-merge (squash) May 24, 2024 23:27
@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented May 24, 2024

Datadog Report

Branch report: backport-9387-to-2.9
Commit report: 98b61b3
Test service: dd-trace-py

✅ 0 Failed, 8358 Passed, 50223 Skipped, 3h 14m 40.79s Total duration (5h 46m 34.95s time saved)

@Yun-Kim Yun-Kim merged commit 079f76d into 2.9 May 28, 2024
152 of 154 checks passed
@Yun-Kim Yun-Kim deleted the backport-9387-to-2.9 branch May 28, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants