Node.js profiling: high usage in "(program)" section

Question

Configuration:

• Node.js 0.8.15
• Mac OSX 10.7.5
• Webkit Devtools Agent node module

While profiling, I've noticed a very high utilization in the "(program)" section of the profile. "Manually" profiling (with node --prof and mac-tick-processor) shows a similarly high percentage spent in ___psynch_rw_unlock in the C++ section.

The primary usage of the program during the profiling was:

• libxml processing
• tls socket reading / writing
• mongodb writing

Is this normal behavior, or is this a sign of a deeper problem?

Answer 1

As of now, Chrome classifies both native code and idle time as (program). Now that http://trac.webkit.org/changeset/138004 has landed, let's see if it makes it into the next Chrome version...