Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

nodejs profiling; what can 'Unknown' be

nodejs profiling; what can 'Unknown' be

Problem

While Profiling a Nodejs program, I see that 61% of the ticks are caused by 'Unknown' (see below). What can this be? What should I look for?

gr,

Coen

Statistical profiling result from node, (14907 ticks, 9132 unaccounted, 0 excluded).

 [Unknown]:
   ticks  total  nonlib   name
   9132   61.3%

 [Shared libraries]:
   ticks  total  nonlib   name
   1067    7.2%    0.0%  C:\Windows\SYSTEM32\ntdll.dll
     55    0.4%    0.0%  C:\Windows\system32\kernel32.dll

 [JavaScript]:
   ticks  total  nonlib   name
   1381    9.3%   10.0%  LazyCompile: *RowDataPacket.parse D:\MI\packet.js:9
......
Problem courtesy of: coen

Solution

You are using a 64 bit version of Node.JS to run your application and a 32bit build of the d8 shell to process your v8.log. Using either a 32 bit version of Node.JS with ia32 as the build target for the d8 shell or a 64 bit version of Node.JS with x64 as the d8 shell build target should solve your problem.

Solution courtesy of: user2161217

Discussion

View additional discussion.



This post first appeared on Node.js Recipes, please read the originial post: here

Share the post

nodejs profiling; what can 'Unknown' be

×

Subscribe to Node.js Recipes

Get updates delivered right to your inbox!

Thank you for your subscription

×