Re: FastCGI 'failed to remain running for 30 seconds' due to max_requests / & Why dynamic?

Tim Wood <timwood0@...> writes:
> This seems like the basic problem, esp. as you talk
> about high volume later.  Applications/platforms
> should not leak memory, especially ones expected
> to sustain high loads over time.

PHP admitedly uses a lot of libraries, so it's a good safety break either way. 
I really don't mind that functionality, however would want to tweak the
settings.  I am fairly confident that this is the setting I want to tweak (in my
'this is what I tried' section), but it doesn't seem to take effect.

I am not suggesting that this is going to be common (keep in mind this is going
to a small number of PHP interpreters at this point simply displaying <?
phpinfo(); ?>).  We do have customers sometimes who put their sites into
apachebench and run a few thousand requests in a matter of seconds.  Then there
is of course DoS issues where one could do that.  It's just not acceptable for
ANY application to give up that early, and for that long in a public server
environment.  I'd have customers calling me left-right-and-center for 10
minutes, and I'd have to rehash Apache.  I guess I'm looking for a tweak.



Which had me looking into the issue further and wondering why it wasn't spawning
the application with my settings to start with. Why is it starting a dynamic
application if a static one is already set up?


-M

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/