重置应用程序池时会发生什么? [英] What happens on an application pool reset?

问题描述

在IIS 7中回收应用程序池时会发生什么? IIS会突然停止该网站上的所有内容并且对用户产生影响吗?还是透明地进行操作，使用户永远不会注意到任何东西?

What happens when an application pool is recycled in IIS 7? Does IIS abruptly stops everything on that website and there is user impact or does it does it transparently and the user never notices anything?

我们应该完全回收吗?它的优缺点是什么?

Should we do recycles at all? What are the pros and cons of it?

我想每天晚上很晚才去做这件事，因为那时人流量很低.有什么最佳做法和建议吗?

I was thinking of doing it everyday late at night when traffic is very low. Any best practices, suggestions?

谢谢

推荐答案

如果您的意思是应用程序池回收"，那么它是一个在线操作.将创建一个新的w3wp进程来处理后续请求，而上一个w3wp进程具有可配置的时间来完成所有未完成的请求(默认为90秒).因为必须重新加载内存中的项目，但不会造成中断，因此会对性能产生影响.

If you actually mean Application Pool Recycle, then it is an online operation. A new w3wp process is created which serves subsequent requests, while the previous w3wp process has a configurable amount of time to complete all outstanding requests (by default 90 second). There is a performance impact since the items in memory have to be reloaded, but there is no outage.

如果您遇到内存泄漏问题，则每晚进行一次回收，然后进行某种形式的预热(将项目加载到内存中)是个好主意，但真正的优势是能够在低负荷时进行预热(否则，最好不要在真正需要的时候再利用它.)

Having a nightly recycle, followed by a warm-up of some sort (to load items into memory) is a fine idea if you have memory leak issues, but the real advantage is the ability to warm-up during low-load (otherwise you're better off to not recycle till it's actually necessary).

如果您实际上是指Reset(通常称为IIS Reset，或者对于Application Pool来说是停止，然后启动)，则是的，这是断电.而且，如果可以避免，则不应这样做.

If you actually mean Reset (which is normally said as an IIS Reset, or for an Application Pool a stop, then start) then yes, there is an outage. And no, it should not be done if it can be avoided.

这篇关于重置应用程序池时会发生什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！