On Thu, Oct 4, 2012 at 6:22 PM, Chris Dew <[email protected]> wrote: > I'm starting to have a speed problem with a production NodeJS application > (20-100% cpu usage). > > I've run it with --prof and used node-tick-processor. > > Is 91% of ticks in libc 'normal'?
It can be, if your application spends a lot of time waiting for new events in epoll_wait(). A quick way to check that is `strace -c node app.js` and `time node app.js`. One prints a tally of system calls, the other a breakdown of system vs. user time. > P.S. is there a way to show the 'unaccounted' ticks? I expect it needs to > be told where to find the source of the app. Not that I know of. I don't think it's due to missing sources. Unaccounted ticks are ticks where V8's profiler thread was not able to make sense of either the instruction pointer or the stack pointer. -- 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
