Feature #375
closeda way to include PHP module at startup time
Description
such as mod_php - this way there is no needing an interim fastcgi dispatcher. just about everything i use has PHP in it, so this would be great because it would load the php footprint each time a new process starts and not every time a new fcgi needs to be spawned.
-- mike
Updated by jan over 19 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Sorry,
1. The FastCGI process stays up all the time. No extra spawning on request-base
2. Including a mod_php would be a very bad idea as a single 'sleep(1000);' would block the whole server.
3. Apache + mod_php is slower than lighttpd + fastcgi-php
Updated by Anonymous over 18 years ago
- Status changed from Fixed to Need Feedback
- Resolution deleted (
invalid)
well, i doubt that fastcgi-php is faster then apache, since we have tried it with oscomemrce, and lighty takes about 10times for for a single page display...
Updated by jwmcglynn about 18 years ago
- Status changed from Need Feedback to Fixed
- Resolution set to invalid
Embedding a PHP interpreter into the server would go against the strategy of having a single-threaded process. If mod_php was embedded into lighttpd the server wouldn't be able to handle any requests while PHP is being interpreted, resulting in a far slower server than Apache.
Replying to anonymous:
well, i doubt that fastcgi-php is faster then apache, since we have tried it with oscomemrce, and lighty takes about 10times for for a single page display...
Benchmarks have shown that FastCGI with lighttpd is just as fast as mod_php is with Apache: http://schlitt.info/applications/blog/index.php?/archives/504-Apache-vs.-Lighttpd-echo-performance.html. Perhaps you are confusing CGI with FastCGI? CGI has to start the PHP interpreter each time, FastCGI does not.
If you continue to have problems with using fastcgi-php please compare your PHP configuration against the one that mod_php uses.
Also available in: Atom