David Sanchez

@nat45928 many thanks for trying that out! That eliminates one potential angle.

Hi again, everyone. I have an x86_64+glibc release of ddtrace available, if anyone is interested in trying it out here. I had to host it out of a personal repo...

Good catch, @majorgreys , and thank you for the report @LukeZeller . This definitely seems like a Profiler issue, and one which should be easy to remediate.

Oh wow, just saw this--really cool 8)

👋 `perf` and `ddprof` have similar overheads, so I think I can answer this one. There are a few different sources of overhead, but generally speaking it works out like...

👋 thank you for the report! Can you confirm the ddtrace version which is causing issues? Also, I can't quite see the top of the dashboard, but it looks like...

@micahjz thank you for the report. I received another report about this today; investigating. Just to double-check, when you wrote > `DD_PROFILING_STACK_V2_ENABLED=false` Did you mean > `DD_PROFILING_STACK_V2_ENABLED=true`? Generally, for overhead-related...

@micahjz thank you for checking it out and the comprehensive report. I think there might be something actionable here, but I need to run some of my own experiments to...

@micahjz are there any details you can share about the structure of your application? Is it using threads? Tasks? One short-lived thread per request? One short-lived ConcurrentFuture worker per request?...

> I want to make sure its clear that we were already running with profiling enabled Appreciate the clarification--thank you--I misunderstood the original message to mean that the overhead was...