“固定数量的请求”之后的应用程序池回收 [英] Application pool recycle after "Fixed number of requests"

问题描述

在固定数量的请求之后，IIS的应用程序池设置对回收再循环有什么影响？

What are the effects of IIS's app pool setting for recycling to recycle after "Fixed number of requests"?

假设这个数字是100，并且第99个人连接到我的网站，那么第100个人来了并将触发应用程序池回收。

Suppose this number is 100, and the 99th person connects to my web site, then the 100th person comes and will trigger an application pool recycle.

这是否意味着会话1-99的所有会话信息都将丢失（进程内会话将在应用程序池工作进程重新启动时到期）？

Does this mean all session information for sessions 1-99 will be lost (in-process session will expire when application pool worker process restarts)?

推荐答案

你基本上是正确的，但这不是人，而是请求。在您的应用程序上调用的每个aspx页面都会累加，当达到阈值时，应用程序池将被回收，应用程序域（如果您使用.Net）将被卸载并且所有内容都会重新启动。您将丢失会话，应用程序和任何静态变量。如果你使用经典的asp或php，那么每个会话和全局变量都会丢失。

You basically have it right, but it's not the person, it's the request. Each aspx page called on your application will add up and when the threshold is reached, the application pool is recycled, the application domain (if your using .Net) is unloaded and everything starts up again. You lose Session, Application and any static variables laying around. If your using classic asp or php, every session and global variables are lost too.

一些命中阈值有点矫枉过正。您应该禁用它或将其设置为一个庞大的数字。默认情况下，如果我没记错的话，如果没有请求，IIS6应用程序池每15分钟回收一次，您还可以在应用程序用于触发回收的总内存上设置阈值。

A number of hits threshold is a bit overkill. You should either disable it or set it to a huge number. By default, if I recall well, the IIS6 application pool recycles every 15 minutes if there were no request and you can also put threshold on the total memory used by your application to trigger recycling.

这篇关于“固定数量的请求”之后的应用程序池回收的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！