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.

Sign up for GitHub

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

Jump to bottom

ddtrace==2.13.1 profiler issue #11069

Open
doudoujay opened this issue Oct 17, 2024 · 0 comments
Open

ddtrace==2.13.1 profiler issue #11069

doudoujay opened this issue Oct 17, 2024 · 0 comments

Comments

@doudoujay
Copy link

doudoujay commented Oct 17, 2024 •
edited
Loading

After i updated our docker's ddtrace from ddtrace==2.9.3 to ddtrace==2.13.1, we observed some weird behaviors on profiler.
We upgraded on Oct 11.

Heap - Bytes in Use drop to 0
Image
Image

Allocated Bytes Significantly increased -
Image
Image
Huge chunk of memory consumed by periodic ensure_binary

Increased CPU Time
Image
Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@doudoujay