是否有任何原因不减少 IIS 7 中的 Ping 最大响应时间
IIS 包含一个工作进程健康检查“ping”功能，默认情况下每 90 秒对工作进程执行一次 ping 操作，如果工作进程没有响应，则回收它们。我有一个应用程序长期将应用程序池置于不良状态，我很好奇是否有任何理由不降低此时间以强制 IIS 更快地回收失败的工作进程。我在网上搜索时发现，人们正在增加调试时间。对于 Web 应用程序来说 90 秒似乎太长了，但也许我错过了一些东西。
IIS includes a worker process health check "ping" function that pings worker processes every 90 seconds by default and recycles them if they don't respond. I have an application that is chronically putting app pools into a bad state and I'm curious if there is any reason not to lower this time to force IIS to recycle a failed worker process quicker. Searching the web all I can find is people that are increasing the time to allow for debugging. It seems like 90 seconds is far to high for a web application, but perhaps I'm missing something.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
显而易见的答案是，在某些情况下，工作进程需要 90 秒以上的时间才能返回请求。如果您无法想象这种情况是否合适，请随意降低它。
我不建议将时间设置得低于 30 秒。我可以看到你陷入回收循环的情况。不过，您可以进行测试，看看什么对您的情况有意义。我建议使用 Siege 进行负载测试，以了解应用程序的行为。
Well the obvious answer is that in some situations requests would take longer than 90 seconds for the worker process to return. If you can't imagine a situation where this would be appropriate, then feel free to lower it.
I wouldn't recommend going too much lower than 30 seconds. I can see situations where you get in recycle loops. However you can do testing and see what makes sense in your situation. I would recommend Siege for load testing to see how your application behaves.