I am trying to profile node-dbus by creating a v8.log and running the mocha test through node-tick-processor. I've got the output no problem, but trying to glean information out of the produced log is proving difficult.
Would you be able to help me understand where node-dbus is spending most of it's time?
Statistical profiling result from v8.log, (132 ticks, 0 unaccounted, 0 excluded).
Hi Andrey,
I am trying to profile node-dbus by creating a v8.log and running the mocha test through node-tick-processor. I've got the output no problem, but trying to glean information out of the produced log is proving difficult.
Would you be able to help me understand where node-dbus is spending most of it's time?
Statistical profiling result from v8.log, (132 ticks, 0 unaccounted, 0 excluded).
[Shared libraries]: ticks total nonlib name 82 62.1% 0.0% /usr/lib64/libv8.so.3.14.5 24 18.2% 0.0% /usr/bin/node 16 12.1% 0.0% /usr/lib64/libc-2.20.so 1 0.8% 0.0% /usr/lib64/libpthread-2.20.so
[JavaScript]: ticks total nonlib name 1 0.8% 11.1% Stub: FastNewContextStub 1 0.8% 11.1% Stub: BinaryOpStub_SHR_AllocSMI 1 0.8% 11.1% RegExp: ^(\/?|)([\s\S]?)((?:.{1\,2}|[^\/]+?|)(.[^.\/]_|))(?:[\/])$ 1 0.8% 11.1% LazyCompile: ~unmarshall /home/username/node-dbus/lib/message.js:61 1 0.8% 11.1% LazyCompile: ~toString native v8natives.js:223 1 0.8% 11.1% LazyCompile: test /home/username/node-dbus/test/unmarshall-basic.js:8 1 0.8% 11.1% LazyCompile: APPLY_PREPARE native runtime.js:438 1 0.8% 11.1% LazyCompile: writeSimple /home/username/node-dbus/lib/marshall.js:107 1 0.8% 11.1% LazyCompile: *append _linklist.js:63
.... rest of file....