4 ms·
I’ve been working in a Node codebase for a bit, and I am really missing Go’s built-in profiler and benchmarking support. It’s pretty well integrated into the de
by lacker 7y ago
I’ve been working in a Node codebase for a bit, and I am really missing Go’s built-in profiler and benchmarking support. It’s pretty well integrated into the default tooling, and easy to use.
- XCSme 7y agoWhat about using the Chrome Dev Tools for Node profiling?
- lacker 7y agoThe node tools & chrome dev tools just seem very poorly integrated by comparison with the go tools. In go, if you have a unit test and you want to profile the code in it, it's just a few code changes to set that up. To use the chrome dev tools, you have to connect to some running process with a browser, which requires at least rearchitecting whatever you're doing so that it's an indefinitely running process. The built-in node profiling is sort of medium in ease of use, but low quality in the information it returns. Often it's hard to figure out what high-level function calls correlate with the low-level performance info.