You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our very large Django app we have some views that manage to get 10s of thousands of spans from the ddtrace django integration wrapping django/forms/widgets/attrs.html and django/forms/widgets/select_option.html.
We upgraded from 2.9.4 to 2.19.3 at the start of the month and we noticed that the latency on these views went from a couple seconds to 25 seconds.
After releasing a number of the intervening versions we discovered that the performance penalty happens when upgrading past 2.14.7.
It is unclear exactly why and it appears we can't selectively not wrap specific templates.
I may need some assistance in figuring out what information you would need that may be helpful to understand what is happening here and what a fix could look like.
Reproduction Code
No response
Error Logs
No response
Libraries in Use
No response
Operating System
python:3.12.9-slim-bullseye docker image Linux 6.1.124 #1 SMP PREEMPT_DYNAMIC Sat Jan 25 00:17:27 UTC 2025 x86_64 GNU/Linux
Debian 11.11
The text was updated successfully, but these errors were encountered:
Is there any further information you could provide such as:
a) Which integrations are you using with django?
b) How are you enabling django tracing? (i.e. are you using ddtrace-run or import ddtrace.auto)?
c) Is there any sample reproduction, such as a sample of your app, that you could provide (which might be related to the latency spike)?
Any information would help us to investigate the issue further!
Tracer Version(s)
2.15.0+
Python Version(s)
Python 3.12
Pip Version(s)
latest/uv
Bug Report
Hello,
In our very large Django app we have some views that manage to get 10s of thousands of spans from the ddtrace django integration wrapping
django/forms/widgets/attrs.html
anddjango/forms/widgets/select_option.html
.We upgraded from 2.9.4 to 2.19.3 at the start of the month and we noticed that the latency on these views went from a couple seconds to 25 seconds.
After releasing a number of the intervening versions we discovered that the performance penalty happens when upgrading past 2.14.7.
It is unclear exactly why and it appears we can't selectively not wrap specific templates.
I may need some assistance in figuring out what information you would need that may be helpful to understand what is happening here and what a fix could look like.
Reproduction Code
No response
Error Logs
No response
Libraries in Use
No response
Operating System
python:3.12.9-slim-bullseye docker image
Linux 6.1.124 #1 SMP PREEMPT_DYNAMIC Sat Jan 25 00:17:27 UTC 2025 x86_64 GNU/Linux
Debian 11.11
The text was updated successfully, but these errors were encountered: