I tried to profile my nodejs based UI server.js file with the internal nodejs profiler(activated via "--prof" tag) and also I tried to profile it separately via v8-profiler. After switching on the profiler, I ran a stress testing script to test the load on my server.js file, but after a few minutes (10-15 mins) my nodejs based UI server becomes unresponsive. Though I can still see the process running in the env but it becomes completely unresponsive. I need to gather nodejs CPUProfile for analysis of my UI nodejs server (for an interval of 2 hours). Have anyone faced such similar issue? If not, still can anyone tell me why is that happening and how to deal with it?
via Anubhav Mahajan
No comments:
Post a Comment