Windows Server 2003 - 空闲时保持运行
我目前正在将网站移动到新服务器，同时我注意到设置 com+ 应用程序组件在空闲时运行的选项。
目前，此选项在所有组件上都设置为 true，但在我看来，似乎需要进行某种权衡（页面加载时间与服务器压力）。
有谁知道这些选项的实际优点和缺点是什么？
I'm currently moving a website to a new server, whilst doing so i've noticed the option to set com+ application components running when idle.
This option is currently set to true on all components, but it sounds to me like there would be some sort of trade off (page load time vs strain on server).
Does anybody know what the realitve pros and cons are of these options?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我猜您正从 Windows 2000 迁移到 Windows 2003。在 IIS6 网站（以及其中定义的应用程序）上，现在使用 IIS 管理器中定义的应用程序池的专用概念，而不是使用原始的 COM+ 应用程序。
但是，在这两种情况下，如果进程空闲一段时间（即没有处理任何请求），都可以选择关闭该进程。
好处是进程占用的内存和其他资源被释放。
缺点是在用户请求等待时再次旋转进程并恢复任何应用程序级数据的成本。
对于 Intranet 应用程序或服务器专用于为一小组特定站点提供服务的情况，启用空闲超时可能不是一个好主意。
如果您有数十或数百个网站，则可能在 IIS6 上的同一应用程序池中托管这些网站组，因此再次启用空闲超时可能是无效的。
我唯一一次看到它有用的是一个执行一些繁重操作的网站，很少使用并安装在具有其他职责的服务器上。
I'm guessing you are moving from Windows 2000 to Windows 2003. On IIS6 Web sites (and applications defined within them) now use a dedicated concept of an Application Pool defined within IIS manager rather than use the original COM+ applications.
However in both cases there is an option to shutdown the process if it has been idle (that is no requests have been processed) for a period of time.
The upside is that the memory and other resources being occupied by the process is released.
The downside is the cost of spinning the process back up again and the restoring of any application level data whilst a user request is waiting.
For intranet applications or where the server is dedicated to serving a small set of specific sites enabling idle timeout is probably not a good idea.
Where you have dozens or hundreds of websites you probably host groups of these in the same application pool on IIS6 so again enabling idle timeout is probably ineffectual.
The only time I could see this being useful is a website that performs some heavy operations, is rarely used and installed on a server that has other duties.