performance - How to keep my ASP.NET app always "alive", and if its a bad idea, why shouldn't I do it? -
I recently posted the ASP.NET application on my shiny new VPS and I am happy with normal performance growth That a VPS can give to a shared hosting solution, I am unhappy with the startup time of my application.
It takes a reasonable time to start my web application when my client first hits it. I'm not running it in debug mode (disabled in my web.config), and doing it at startup There is no real work for - I do not have any code in the event handler that launches the application, I do not start any extra threads, nothing is the first time my client has hit my application. Or, it is the best time of 15-20 seconds to answer. The latter call takes 1-2 seconds, until I wait a few minutes to close my application. Then it comes back at 15-20 seconds at startup time.
(I know that my time benchmark is extremely unscientific, those numbers should feel to be displayed at the time of my app's startup). So, after the preface of the size of that book, my questions are: Thank you! Edit: It seems that my question is a bit duplicate (I thought I did a better job of searching for an answer on it, here) It seems that my question is more comprehensive, and I appreciate that if it has not been stopped as a duplicate, as long as it is not good, already know the questions given here.
IIS also closes its web app after a certain time period, based on its configuration I'm not familiar with IIS7 and where to configure it, so you might want to do some research on how to configure this ().
Is it bad? It depends how good your code is, if you are not leaking out of memory or resources, maybe not.
The second solution is that it can be a better option for you.
Comments
Post a Comment