I have a problem with a website that is hosted on a Windows Server 2008 R2 server (equipped with an Intel Xeon QuadCore processor and 12 GB of RAM).
Two weeks ago, every day (and several times a day) we must restart the website (from the IIS) so that it starts working again.
Prior to the restart, the peculiarity is that after trying to login to the website it stops responding and "waiting" for authentication (it does not even connect to the database where authentication must be verified). It does not even throw an error that allows us to identify the problem because it remains "infinitely" "waiting".
This happens to many users of the website and when it is restarted everything returns to normal.
Before restarting it, we verify and see the following:
- Both% CPU consumption and server RAM are low.
- There are no DDos attacks or anything like that.
- The website has its own assigned Application Pool and is running.
We have even changed the server website (one with identical characteristics) and the same thing happens to it.
Analyzing the coding of the website I see that it makes excessive use of session variables with respect to its quantity and size of saved data. But, beyond this terrible practice, we are not sure that this is "the inconvenience".
How and where can I detect if the website reaches a peak performance and flies through the air? Knowing that the server where you run is not at your capacity limit?
Thank you very much.