克服汇编（？）暂停对* *二次初始ASP.Net应用程序的启动？ [英] Overcome compilation(?) pause on *secondary* initial ASP.Net application startup?

问题描述

部署ASP.Net应用程序到一个新的服务器后，第一个用户击中的应用因执行其初始编译得到一个长时间的停顿，presumably。然而，这似乎停顿也还出现在应用程序超时，并从内存中卸载本身了。

After deploying an ASP.Net application to a new server, the first user to hit the app gets a long pause, presumably because the app is performing its initial compilation. However, this pause seems to also also occur after the application has timed out and unloaded itself from memory.

第一次编译会容忍的，因为它只有happpens一次，但第二人似乎对我来说，它应该是不必要的....有一种变通方法来解决这个问题？这将是很好能够延长应用程序超时，但我只看到一个方法来扩展会话超时，我宁愿不做，因为这将让所有用户会话在内存中的很长一段时间。

The first compilation would be tolerable as it only happpens once, but the 2nd one seems to me like it should be unnecessary....is there a workaround to address this issue? It would be nice to be able to extend the application timeout, but I only see a way to extend the session timeout, which I would rather not do, as this would keep all user sessions in memory for a long period of time.

推荐答案

这是IIS关闭工作进程 - 默认值是20分钟的空闲时间。在IIS6，您可以配置<一个href=\"http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/83b35271-c93c-49f4-b923-7fdca6fae1cf.mspx?mfr=true\"相对=nofollow>应用程序池，并关闭空闲超时（性能选项卡上）。在IIS7，它在高级设置。

That's IIS shutting down the worker process - the default is a 20 min idle time. In IIS6, you can configure the app pool and turn off the Idle timeout (on Performance tab). In IIS7, it's in the Advanced Settings.

这篇关于克服汇编（？）暂停对* *二次初始ASP.Net应用程序的启动？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！