09-07-2018, 06:52 PM
Hi guys,
I have an Intraweb web database that is generally working well.
The only problem is that users experience a few seconds delay if they request after some time of inactivity.
E.g.... a user works with the web DB and it is blazingly fast, then he does for some minutes nothing with the web DB and when he then starts to work with the web DB again it takes
approx. 10 seconds before the web DB answers (like as if it was waking up again), then everything is blazingly fast again till the next time of inactivity of the user...
I have set KeepAlive to true for all forms and the server controller, I setup the ISAPI application pool so that it should be awake always ...
StartMode: AlwaysRunning
IdleTimeout is set way higher than the time of user inactivity ...
The deployment is done on an Azure VM ...
all Energy settings are set, so that no idle timeouts of CPU or something should happen.
Had anybody ever such issues? How would you go about circleing in in the problem?
I have an Intraweb web database that is generally working well.
The only problem is that users experience a few seconds delay if they request after some time of inactivity.
E.g.... a user works with the web DB and it is blazingly fast, then he does for some minutes nothing with the web DB and when he then starts to work with the web DB again it takes
approx. 10 seconds before the web DB answers (like as if it was waking up again), then everything is blazingly fast again till the next time of inactivity of the user...
I have set KeepAlive to true for all forms and the server controller, I setup the ISAPI application pool so that it should be awake always ...
StartMode: AlwaysRunning
IdleTimeout is set way higher than the time of user inactivity ...
The deployment is done on an Azure VM ...
all Energy settings are set, so that no idle timeouts of CPU or something should happen.
Had anybody ever such issues? How would you go about circleing in in the problem?