Recipe: Profiling JavaScript* code in Node.js* with VTune

Analyzers

Community support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)

Recipe: Profiling JavaScript* code in Node.js* with VTune

248 Views

Hi,

I am Denis Pravdin, Software engineer VTune Amplifier team. At present, I am driving the development of profiling capabilities for Java/native applications and JIT runtimes (e.g. Node.js, HHVM, etc) running in Docker, LXC, and other types of isolation environments. I am looking forward to discuss your use cases and get your feedback on existing Container support in VTune Amplifier.

We have already published an article "How to profile a Java* application in the Docker* container". Any feedback?

Our next article, "Profiling JavaScript* code in Node.js”, is to help you benefit from different VTune Amplifier analysis types (Advanced Hotspots, Memory, Disk I/O, etc) and profile both Node.js internals and JavaScript applications.

If you have any questions, don’t hesitate to ask me directly in this thread.

Thanks, Denis.

Link Copied

0 Replies

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.