On Wed, Apr 4, 2012 at 03:30, Satyam Shekhar <[email protected]> wrote: > > On Wed, Apr 4, 2012 at 3:30 PM, Ben Noordhuis <[email protected]> wrote: >> >> On Wed, Apr 4, 2012 at 02:46, Vineet Gupta <[email protected]> >> wrote: >> > Got the output given below from the V8 profiler. Note the first line >> > which >> > indicates a memory range. In our case this is contributing to most of >> > our >> > CPU utilization (95%) >> > >> > What is the meaning of this memory address range in the V8 output. Is >> > there >> > a way of mapping this to our codebase? >> >> It's the address of the VDSO, the kernel gate so to speak. I wager >> that your application spent most of its time sleeping in epoll_wait(), >> i.e. was mostly idle. You can verify that with `strace -c`. > > > Hey, > > I am working on the same project. I have a follow up question. > > When we ran the application and monitored the cpu consumption using top, we > noticed the utilization to be greater than 50% (sometimes touching 100%). > Why would that happen if the application is idle?
It depends on your application. If it does a lot of file I/O, it's possible that the main thread is mostly idle while the I/O threads are chugging away. `strace -c` and `strace -cf` profile syscalls. The first one profiles just the main thread, the second one profiles threads and child processes. -- 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
