是什么导致 IIS 中的应用程序池回收? [英] What causes an application pool in IIS to recycle?

问题描述

我一直在寻找有关这方面的信息，但无济于事.为什么我需要这个的背景是我在这里问的另一个问题.更具体地说，在 App_Data 中创建/更新/删除文件是否会导致池回收?

I have been searching for info on this to no avail. The context of why i need this is another question I asked here. More specifically, does creating/updating/deleting files in App_Data cause a pool recycle?

如果有人能提供导致回收的详细列表，那就太好了.

If someone could provide a detailed list of what causes a recycle, that would be great.

更新:正如两位用户已经注意到的那样，我也很乐意回答指定仅回收 AppDomain 而不是整个池的原因.

UPDATE: As two users already noticed I would also be happy to an answer specifying reasons for recycling the AppDomain only and not the whole pool.

推荐答案

两种不同的效果:

• AppPool 进程是潜在多个 AppDomain 的宿主.通常，这可以通过多种效果进行回收.这些可能是时间(每 n 小时)、缺少请求、内存使用等；全部在 IIS 配置管理器中配置.

• The AppPool process is the host for potentially multiple AppDomains. Typically this can be recycled by a number of effects. These could be time (every n hours), lack of requests, memory use, etc.; all configured in IIS Config Manager.

应用程序根的托管实例 AppDomain 可以更频繁地循环，而不会影响 AppPool 中的其他 AppDomain.Tess 关于 AppDomain 回收的帖子 非常有见地.

The AppDomain, the hosted instance of your application root, can be cycled more frequently without affecting other AppDomains in the AppPool. Tess's post on AppDomain recycling is pretty insightful.

您正在写入一个监视重新编译的文件夹.这将在某个时候触发 AppDomain 重新创建.

You are writing to a folder monitored for recompilation. This will trigger the AppDomain recreation at some point.

事件日志将帮助您确定启动回收的原因.

The event log will help you determine what cause initiated the recycle.

这篇关于是什么导致 IIS 中的应用程序池回收?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！