I would recommend profiling the application to find where it spends most of it's time and then debugging, or you could do the later first.
Checkout https://github.com/node-inspector/node-inspector for debugging you app. For profiling you could use a service like LoopBack or NodeTime, or do it yourself. I personally prefer to run node with --prof and run the v8 profiler on the resulting fille (https://code.google.com/p/v8/wiki/V8Profiler). On Thursday, May 29, 2014 1:15:44 AM UTC-3, Reza Razavipour wrote: > > I have a RESTful node server. Clients send requests which all translate to > SOAP calls. The SOAP server and node server all both on the same machines. > One HTTPS request, all are HTTPS, can translate into up to 7 SOAP calls. > > When the client puts the auto refresh on, every 5 seconds a series of > requests are sent to the node server. With 2 clients, auto refresh on, can > add up to two dozens of SOAP calls, > the node server, using top, goes up above 80%. > > How can I determine what is causing this CPU spike? 2 dozens of SOAP calls > can cause this? > > > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/5b1d44c0-26fc-4fd6-94e8-d559d544fe90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
