Kunal Nain

@vijayghaghre Any updates on this issue? Were you able to resolve it?

@timanderson Sorry for not replying back to you earlier. I did a little bit of local testing with 6 attendees in the meeting. I am using the serverless demo that...

@timanderson Sorry missed one thing in my previous comment. You are using Firefox and not Chrome. Sorry I used Chrome by habit. Following is the screenshot of usage on Firefox....

Hey @timanderson, Currently, I do not know the reason for the high CPU consumption. I will log this as a bug and will track it in the backlog. After doing...

@keean, A couple of questions about this fix. I will like to add some documentation for other builders who might run into the same issue. - What bug fix in...

@keean I have raised a PR to update the FAQ guide. Please feel free to review the PR as you have context and knowledge about this issue. Thank you for...

@keean That makes sense. I think that lines up with the FAQ I wrote. BTW please feel free to review my PR. I will appreciate your feedback since you have...

@aniltomar10 Are you talking about server inactivity timeout? If you are then IISNode timeout is close to 20 minutes. Sending ping or dummy HTTP request to your API every 5...

@msi-matthew I think this issue is coming from your mssql package. IISNode usually does not throw errors like these. [email protected] was released in 2016 and I would recommend updating the...

@msi-matthew The issue can also be because of IISNode's internal code (Interceptor.js). Check this issue: [https://github.com/Azure/iisnode/issues/60](https://github.com/Azure/iisnode/issues/60).