回收工作进程对WCF服务的影响
我想知道回收工作进程 (IIS V 6.0) 对 IIS 中托管的 WCF 服务有何影响（在性能、可用性等方面），我还想知道是否有关于如何配置的最佳实践回收时间或请求数。
我还想知道被回收的工作进程是否与实例化配置设置为 Single 的服务有关，是否需要在每次工作进程回收后再次实例化它？
谢谢！
i want to know what is the impact (in performance, availabillity, etc) that Recycling the Worker Process (IIS V 6.0) has over a WCF Service Hosted in IIS, i would also like to know if there's a best practice on how to configure the recycling time or # of requests.
I would also like to know if the Worker Process being recycled has something to do with an service that it's instantiation configuration is set to Single, does it has to instantiate it again after every worker process recycling?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
http://msdn.microsoft.com/en-us/ library/ms525803(VS.90).aspx 注释：
回收应用程序时的注意事项
回收应用程序时，会话状态可能会丢失。在重叠回收过程中，也有可能发生多实例。
会话状态丢失：许多 IIS 应用程序依赖于存储状态的能力。如果 IIS 6.0 自动关闭因空闲处理而超时的工作进程，或者在回收期间重新启动工作进程，则可能会导致状态丢失。
多实例的发生：在多实例中，一个进程的两个或多个实例同时运行。根据应用程序池的配置方式，工作进程的多个实例可能会运行，每个实例可能加载并运行相同的应用程序代码。重叠回收的发生是多实例的一个例子，就像网络花园一样，其中两个或多个进程为应用程序池提供服务，而不管回收设置如何。
如果您的应用程序无法在多实例环境中运行，则必须为应用程序池仅配置一个工作进程（这是默认值），并且如果使用应用程序池回收，则禁用重叠回收功能。
我鼓励您阅读 MSDN 上与您的问题相关的文章，此外，它们应该有西班牙语翻译，以帮助解决与难以理解英语和技术术语相关的问题。
http://msdn.microsoft.com/en-us/library/ms525803(VS.90).aspx notes:
Considerations When Recycling Applications
When applications are recycled, it is possible for session state to be lost. During an overlapped recycle, the occurrence of multi-instancing is also a possibility.
Loss of session state: Many IIS applications depend on the ability to store state. IIS 6.0 can cause state to be lost if it automatically shuts down a worker process that has timed out due to idle processing, or if it restarts a worker process during recycling.
Occurrence of multi-instancing: In multi-instancing, two or more instances of a process run simultaneously. Depending on how the application pool is configured, it is possible for multiple instances of a worker process to run, each possibly loading and running the same application code. The occurrence of an overlapped recycle is an example of multi-instancing, as is a Web garden in which two or more processes serve the application pool regardless of the recycling settings.
If your application cannot run in a multi-instance environment, you must configure only one worker process for an application pool (which is the default value), and disable the overlapped recycling feature if application pool recycling is being used.
I would encourage you to read through those articles on MSDN that pertain to your problem, and additionally, they should have a translation to Spanish to help with issues pertaining to difficulty to understand English with technical jargon.