> Does the linux-tick-processor match the version of node / V8 that
generated the log file?
As in 64b vs 32b? I'm on Ubuntu 12, 32b. I installed v8
from git://github.com/v8/v8.git.
Looks like node.js is 32bit.
arch: 'ia32',
platform: 'linux',
Changelog for v8 says 3.14.5.
13:46 vmplanet@ubuntu /usr/bin/nodejs-0.10.2/deps/v8 $ cat ChangeLog
2012-10-22: Version 3.14.5
I'm not sure if I answered your question.
> Are you using the cluster module?
No.
On Thursday, April 4, 2013 12:33:11 PM UTC-7, Ben Noordhuis wrote:
>
> On Thu, Apr 4, 2013 at 8:07 PM, Justin Collum <[email protected]<javascript:>>
> wrote:
> > I'm using https://github.com/bnoordhuis/node-profiler to do some
> profiling.
> > I've got a chunk of code that pulls in json from a file and performs
> some
> > logic on the objects that get loaded. There are 1000s of objects and a
> > dependency graph, so it takes a good long while. This is a stress test.
> The
> > code looks like:
> >
> >> var profiler = require('profiler');
> >> profiler.resume();
> >> ce.buildDepGraph();
> >> profiler.pause();
> >
> >
> > OK so ce.buildDepGraph is a function that loops the objects from the
> json
> > and builds a dep graph. It all runs fine, but when I run v8.log through
> the
> > linux-tick-processor I get hundreds of lines that look like:
> >
> > line 947: unknown code state: undefined
> >
> > and hundreds more like:
> >
> > Code move event for unknown code: 0x3254c6e0
> >
> > At the end, I get this:
> >
> >
> > Statistical profiling result from v8.log, (9259 ticks, 9259 unaccounted,
> 0
> > excluded).
> >
> > [Unknown]:
> > ticks total nonlib name
> > 9259 100.0%
> >
> > [Shared libraries]:
> > ticks total nonlib name
> >
> > [JavaScript]:
> > ticks total nonlib name
> >
> > [C++]:
> > ticks total nonlib name
> >
> > [GC]:
> > ticks total nonlib name
> > 0 0.0%
> >
> > [Bottom up (heavy) profile]:
> > Note: percentage shows a share of a particular caller in the total
> > amount of its parent calls.
> > Callers occupying less than 2.0% are not shown.
> >
> > ticks parent name
> >
> >
> > Well blech, that's not even remotely useful.
> >
> > I did this profiling without node-profiler and got the same results. Do
> I
> > have to put the actual buildDepGraph code into this test to get it to
> > profile correctly?
>
> Does the linux-tick-processor match the version of node / V8 that
> generated the log file?
>
> Are you using the cluster module? If events from multiple processes
> end up in a single log file, the tick processor output will be bogus.
> Node.js master understands --logfile=%p.log, where %p is replaced with
> the process ID.
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
