从IIS 5迁移到IIS 6后的ASP.NET缓存对象问题 [英] ASP.NET Cache object issues after migration from IIS 5 to IIS 6

问题描述

我遇到一个问题，即每分钟左右清除一次ASP.NET缓存对象.正确的行为是缓存对象应持续24小时.最近，当我们的公共Web服务器从IIS 5升级到IIS 6时，这个问题才开始出现.在高峰时段，该站点每小时可获得约15,000次页面浏览.服务器管理员推测这可能是由于IIS 6中的线程回收造成的.

I'm experiencing an issue where the ASP.NET Cache objects are cleared out every minute or so. The proper behavior is that the cache objects should last 24 hours. This issue started recently when our public web servers were recently upgraded from IIS 5 to IIS 6. The site in question gets about 15,000 page views/hour during peak times. The server admin speculates it could be because of thread recycling in IIS 6.

有什么想法吗?

推荐答案

检查事件日志-它将告诉您该进程是否在回收.

Check the event log - that will tell you if the process is recycling.

假设是这样，我认为当计算机升级到Win2k3/IIS6时，回收极限的某些设置没有移到应用程序池"设置中.在Win2k/IIS5中，回收站设置位于machine.config文件中的processModel节点中.这些设置需要迁移到IIS6环境中的相应应用程序池(我猜这些设置不会自动迁移).

Assuming it is, I'm thinking some settings on the recycle limits weren't moved into the Application Pool settings when the machine was upgraded to Win2k3/IIS6. In Win2k/IIS5, the recycle settings are in the processModel node in the machine.config file. These settings need to be migrated to the appropriate application pool(s) in the IIS6 environment (I'm guessing these settings don't auto-migrate).

我还将查看应用程序池上的回收设置.可能是它设置为经常回收(按分钟数或请求数)，或者最大内存设置太低.

I'd also review the recycle settings on the application pool. It could be that it is set to recycle too often (by number of minutes or number of requests) or that the memory maximums are set too low.

这篇关于从IIS 5迁移到IIS 6后的ASP.NET缓存对象问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！