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
On Node 22 tracing performance when loading the aws-cdk-lib package is severely impacted. For more complex CDK applications, this gets much worst. We have customers reporting an increase from 2 min to over 30 min.
hyperfine -w5 "node20 dd-trace.js" "node22 dd-trace.js"
Benchmark 1: node20 dd-trace.js
Time (mean ± σ): 1.388 s ± 0.015 s [User: 1.470 s, System: 0.104 s]
Range (min … max): 1.361 s … 1.405 s 10 runs
Benchmark 2: node22 dd-trace.js
Time (mean ± σ): 8.826 s ± 0.124 s [User: 9.143 s, System: 0.479 s]
Range (min … max): 8.646 s … 9.022 s 10 runs
Summary
node20 dd-trace.js ran
6.36 ± 0.11 times faster than node22 dd-trace.js
Note that even for node20 performance is kind of slow. Running DD_TRACE_ENABLED=false node22 dd-trace.js brings the execution time up again.
Reproduction Code
Save as dd-trace.js
require('dd-trace').init();constcdk=require('aws-cdk-lib');constapp=newcdk.App();for(leti=0;i<1000;i++){// simulate a large CDK appnewcdk.Stack(app,`DdTraceStack${i}`);}
Error Logs
No response
Tracer Config
No response
Operating System
Darwin Kernel Version 24.3.0
Bundling
Unsure
The text was updated successfully, but these errors were encountered:
Tracer Version(s)
5.40.0
Node.js Version(s)
22.14.0
Bug Report
On Node 22 tracing performance when loading the
aws-cdk-lib
package is severely impacted. For more complex CDK applications, this gets much worst. We have customers reporting an increase from 2 min to over 30 min.Note that even for
node20
performance is kind of slow. RunningDD_TRACE_ENABLED=false node22 dd-trace.js
brings the execution time up again.Reproduction Code
Save as
dd-trace.js
Error Logs
No response
Tracer Config
No response
Operating System
Darwin Kernel Version 24.3.0
Bundling
Unsure
The text was updated successfully, but these errors were encountered: