Bryan English

@Qard If I read that right, there are no events for the response.

In Node.js v16.2.0, significant performance improvements in `async_hooks` are present, so if you can test with this version of Node.js, hopefully that alleviates a lot of the overhead.

You can use our experimental ESM support by using the following command-line flag: ``` --loader=dd-trace/loader-hook.mjs ``` Please let us know in this thread if that resolves this for you.

Hi @jrnail23. In our own tests in this repository, we use [a Node.js mock agent](https://github.com/DataDog/dd-trace-js/blob/master/packages/dd-trace/test/plugins/agent.js). That being said, this isn't very well documented, or particularly suitable for usage outside this...

Hi @jmichel-bc! Usually when this happens, it's because `tracer.init()` was called _after_ `fastify` was required. `tracer.init()` needs to happen _before_ any other `require`s. By default, our HTTP server instrumentation does...

@skimonkey were you able to try on the latest Node.js 16 or Node.js 17, to see if the `async_hooks` fixes help your situation?

Should https://github.com/nodejs/commit-stream be added to this list of repos?

Just a heads up that: 1. This is still something I want to pursue, but don't have a whole lot of time for right now. 2. It should probably be...

@evanlucas For `ulimit -n` I'm seeing 4096 on my Linux machine, 32768 on macOS. @addaleax It looks like it does. I added a sync version of the test to the...

Since the test code here is effectively doing the same thing as a `cp -r`, I thought I'd try timing that in both environments. The script used is in the...