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
ritm.js which gets included in the tree when importing tracer as import tracer from 'dd-trace'; adds about 1s to the startup of any server that uses dd-trace on intel machines. Given that the import of ritm is coming from src/lambda it should not be getting imported when running in a container.
Expected behaviour ritm.js should not be in the import tree in non-lambda environments
Actual behaviour ritm.js is in the import tree in non-lambda environments
Steps to reproduce
import tracer from 'dd-trace'; in any file
take a performance profile in chrome
find the import tree as in the screenshot above
Environment
Docker container deployed via k8s to AWS
Operation system:
Reproduced on macOS
Node.js version:
20.9.0
Tracer version:
N/A
Agent version:
N/A
Relevant library versions: dd-trace v3.39.0 but given the import structure for this path is unchanged on main, this would occur in the latest release as well
The text was updated successfully, but these errors were encountered:
ritm.js
which gets included in the tree when importing tracer asimport tracer from 'dd-trace';
adds about1s
to the startup of any server that usesdd-trace
on intel machines. Given that the import of ritm is coming fromsrc/lambda
it should not be getting imported when running in a container.Expected behaviour
ritm.js
should not be in the import tree in non-lambda environmentsActual behaviour
ritm.js
is in the import tree in non-lambda environmentsSteps to reproduce
import tracer from 'dd-trace';
in any fileEnvironment
Docker container deployed via k8s to AWS
Operation system:
Reproduced on macOS
Node.js version:
20.9.0
Tracer version:
N/A
Agent version:
N/A
Relevant library versions:
dd-trace
v3.39.0 but given the import structure for this path is unchanged onmain
, this would occur in the latest release as wellThe text was updated successfully, but these errors were encountered: