Just re-ran with --log instead of --log-all and as you suggested, it didn't change much about nprof. Results:
v8-lazystartprofiling-ganode.nprof.txt:Statistical profiling result from v8-lazystartprofiling-ganode.log, (9781 ticks, 7212 unaccounted, 0 excluded). v8-lazystartprofiling-patchednode.nprof.txt:Statistical profiling result from v8-lazystartprofiling-patchednode.log, (8799 ticks, 3398 unaccounted, 0 excluded). v8-standardprofiling.nprof.txt:Statistical profiling result from v8-standardprofiling.log, (18120 ticks, 0 unaccounted, 0 excluded). On Friday, October 26, 2012 5:23:24 PM UTC-4, Ben Noordhuis wrote: > > On Fri, Oct 26, 2012 at 10:29 PM, Andrew Spyker > <[email protected]<javascript:>> > wrote: > > One other question, should I be running with --log or --log_all or some > > other version of --log? I'm assuming which I want to run with depends > on > > what I'm trying to profile, but for now I'm trying to get CPU burn. > > --log and --log-all are not mutually exclusive, they log (mostly?) > separate events. > > --log-all is probably most relevant to C++ programmers - V8 developers > in particular :-) - because it logs things that are not user-visible, > like C++ API calls. nprof and tick-processor simply ignore those > events. > -- 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
