node-continuation-local-storage
node-continuation-local-storage copied to clipboard
Question about performance
Hi, is there any information about the overhead/performance impact of using this library?
I'm interested as to whether it's something that could be used on every request of a high QPS service, or whether it's more intended to be used sparingly (for example, a great application of this seems like it would be tracing, and you typically trace some smaller proportion of requests).
This was pulled out of the New Relic APM agent, and has been used in several other APM agents too, so yes, it's usable in that sort of scenario. However, async_hooks-based CLS implementations like cls-hooked are probably better these days.