All geek questions in one place

When profiling NodeJS using --inspect, which means "(program)"

When using node --inspect to profile a NodeJS application using the chrome dev tools, most of the execution time is spent on (program) . I did not find information on what exactly this means? Is it just the time spent on the C ++ part of NodeJS?

+5
source share
1 answer

The (program) element is Chrome itself - this is the first thing that runs before anything else and stays there, regardless of what the Node application does.

This article discusses the Chromium profiler problem about what exactly this means (and whether it is confusing).

You can also see in the Changelog comment for the commit also includes the following comment:

Web Inspector: [Chromium] profiler - distinguishes between its own code (program) and downtime https://bugs.webkit.org/show_bug.cgi?id=88446

NOBODY review (OOPS!).

Now idleTime is provided in the profile object. In this patch, idleTime, if any, is subtracted from the "(program)" node, and the new Node "(idle)" is entered as the top level Node ti profile.

+1
source

Source: https://habr.com/ru/post/1265743/

More articles:


All Articles