profiling with node-profiler & d8: high number of unaccounted ticks

[Vivus Ignis]

Hello noders,

I'm trying to profile my little node app which is effectively a redis proxy. I've required bnoordhuis' profiler module and fed the resulting v8.log to linux-tick-processor. The output seems to me a bit weird:

<SNIP>

Statistical profiling result from /usr/local/repa/v8.log, (31043 ticks, 30884 unaccounted, 0 excluded).

[Unknown]:
ticks total nonlib name
30884 99.5%

(...)

</SNIP>

What does such a high number of unaccounted ticks mean?

p.s.: my host platform is opensolaris, node v0.4.8

Thanks in advance.

[Vyacheslav Egorov]

Is C++ section of the output empty?

If yes then linux-tick-processor for some reason can't resolve ticks
that happen in native code. Maybe something is different with output
format for nm.

--
Vyacheslav Egorov

> --
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/nodejs/-/n1wg_ql1boAJ.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en.
>

[dhruvbird]

Hello,

Maybe related, but I've had a pretty bad experience with the v8
profiler since it is sampling based. Every once in a while, the real
performance problem gets hidden. Not yet as reliable as gprof.

Regards,
-Dhruv.