-
Notifications
You must be signed in to change notification settings - Fork 524
Question: What is the guidance on keeping the application running? #1085
Comments
Your application is likely taking that long on the first request after restart because of view compilation (I assume it's an MVC site?) |
it is MVC site. |
Sure, we're also working on view pre-compilation for 1.1 which is a much better way to avoid compiling views at runtime. |
Hmm if you pre-compile my view, will updating the view still possible on 1.0 you remove updating controller.cs on 1.1 you will remove upading view? |
Yep. We'll you can kinda do it if you use
Nothing is being removed. It's an option you can choose to use. Anyways this has nothing to do with Kestrel. The original question was about keeping the site warm. If you run with IIS you get the usual IIS behavior which is fine for the most part. If you want to keep the application alive then pinging it seems like a fine idea. There's an IIS feature that does application warmup but I'm not sure if it works with ASP.NET Core as yet /cc @pranavkm |
Auto-start is discussed here: aspnet/IISIntegration#161 |
Pinging will do and closed due duplicate |
At this moment, I believe IIS kill the application after inactivity of the application.
The problem is the first request may take 30 seconds or more
The next request is quite fast.
What is the guidance as we have new server now?
Should I ping my website every 5 minutes or so?
Is it still worth it to have IIS to kill my application? (memory management etc)
The text was updated successfully, but these errors were encountered: