我们真的需要重新启动IIS 7应用程序池？难道同样的做法应用到其他Web服务器？ [英] Do we really need to restart IIS 7 application pool? Do the same practice apply to other web servers?

问题描述

我只是想知道为什么重新启动IIS 7应用程序池考虑一个好的做法呢？我知道，这将清理就像线程或会话状态孤儿的资源，但如何做其他的Web服务器处理这类问题？难道Java开发者/管理员必须重新启动WebLogic / websphere的/阿帕奇/ tomcat的，每隔一段时间清理垃圾在内存中？

I am just wondering why is restarting IIS 7 application pool consider a good practice? I know that it'll clean up orphan resources like threads or session state, but how does other web server deal with this kind of problem? Do java developer/admin have to restart weblogic/websphere/apache/tomcat every so often to clean up junk in memory?

推荐答案

通常它被用来弥补不好的编程。有时你，有时是第三方取决于你所使用的库。

Typically it's used to compensate for bad programming. Sometimes yours, sometimes third parties depending on the libraries you are using.

和，与所有的建议，最好看看您的特定环境，看看它是否在做它之前真的有必要。

And, as with all recommendations, it's best to look at your specific environment to see if it's really necessary before doing it.

开始与分析的应用程序。一个简单的方法是只让它运行负载下一段时间。认准的事不一样的内存利用率安家或者它不断成长壮大？

Start with profiling the app. A simple way is to just let it run for a while under load. Look for things like does memory utilization settle down or does it continually grow?

如果它持续增长，你需要设置IIS以如此频繁回收每一个去解决您​​的应用程序。如果它长到一个点，然后稳定下来，那么你应该就好了。请确保您测试甚至你的应用程序的边缘情况。

If it keeps growing, you will need to set IIS to recycle every so often and go fix your app. If it grows to a point then settles down then you should be just fine. Make sure you test even the edge cases of your app.

这篇关于我们真的需要重新启动IIS 7应用程序池？难道同样的做法应用到其他Web服务器？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！