FastCGI进程超出了配置的请求超时-共享主机 [英] The FastCGI process exceeded configured request timeout - Shared Hosting

问题描述

我正在编写一个wordpress插件，该插件在后台执行一些耗时的XML文件处理.在我的机器上，至少需要一个小时.它并不会消耗很多CPU资源，但是速度很慢.

I'm writing a wordpress plugin which do some time consuming XML file processing in the background. On my machine, it takes at least an hour. It doesn't consume at lot of CPU%, but it's just slow.

当我在基于Windows的共享托管上进行测试时，我收到"FastCGI进程超出了配置的请求超时".托管的PHP未在safe_mode中运行.通过大量搜索，我意识到在IIS下作为CGI运行时调用set_time_out()不起作用. IIS在此施加了另一个时间限制.我知道我们可以更改IIS配置带来的限制.但是在共享主机上是不可能的.因此，我正在寻找一种用户可配置的方式，例如在站点的web.config中配置限制.我没有找到任何相关信息，因为大多数IIS用户都拥有服务器.

When I test on my windows based shared hosting, I'm getting "The FastCGI process exceeded configured request timeout". PHP of the hosting is not running in safe_mode. From much searching, I realized that calling set_time_out() does not work when running as CGI under IIS. IIS impose another time limit here. I know that we can change the limit imposed from IIS's configuration. But it's not possible on a shared hosting. Thus I'm looking for a more user configurable way, such as having the limit configure in web.config of my site. I didn't find any information on that as most IIS users own the server.

是否存在这种方法?或者可以采取其他措施来覆盖IIS施加的时间限制.

Does such method exist? Or there's something else can be done to override the time limit impose by IIS.

推荐答案

在共享托管环境中，极有可能无法更改FastCGI请求超时值(作为共享托管者，我们不允许更改此设置)，因为它是服务器范围的设置.

On a shared hosting environment there will most likely not be a way to alter the FastCGI Request Timeout value (as a shared hoster, we don't permit changes to this setting) as it is a server wide setting.

它可以防止像您这样的用户占用宝贵的资源(例如，合并的php-cgi.exe实例)的时间超出您的需要.

It's there to prevent users such as yourself from holding onto valuable resources (such as pooled php-cgi.exe instances) for longer than you need.

即使在可以更改超时(不使用FastCGI的共享环境)中，您也可能会发现许多托管人监视运行时间过长的请求(我们这样做)，并会警告最终用户停止并停止或被禁止.

Also even in shared environments where you can change the timeout (where FastCGI isn't used), you'll probably find out that many hosters monitor for excessively long running requests (we do) and will warn the end user to cease and desist or be banned.

我认为您需要重新考虑插件的工作原理.

I think you need to re-think how your plugin works.

这篇关于FastCGI进程超出了配置的请求超时-共享主机的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！