On Sat, Oct 27, 2012 at 4:23 AM, Andrew Spyker <[email protected]> wrote: > Attached is a third zip of logs based on both patches (and using --log). I > assume the logs help you validate which ticks are coming back as unresolved. > > The second patch doesn't seem to help much more than the first. Still > hovering around 39% of all ticks unrecognized. > > [idcuser@xxxx test-profiling]$ grep Statistical *nprof* > v8-lazystartprofiling-ganode.nprof.txt:Statistical profiling result from > v8-lazystartprofiling-ganode.log, (9667 ticks, 7054 unaccounted, 0 > excluded). > v8-lazystartprofiling-patchednode.nprof.txt:Statistical profiling result > from v8-lazystartprofiling-patchednode.log, (8664 ticks, 3419 unaccounted, 0 > excluded). > v8-standardprofiling.nprof.txt:Statistical profiling result from > v8-standardprofiling.log, (17834 ticks, 0 unaccounted, 0 excluded). > > I guess I should have mentioned, but doubt it matters, that this is on a > cloud instances in the IBM smart cloud, so everything is being run > virtualized (vs. on the metal). Would be interested if someone could repeat > these tests on the metal to see if it skews the numbers at all.
Here is the tracking issue in case you want to follow it: https://github.com/joyent/node/issues/4209 -- 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
