I see most answers believe mod_php is less efficient because memory footprint will be higher due to serving static files,like <a href="https://stackoverflow.com/questions...i-which-is-good-for-wordpress/1943706#1943706">this one</a>.
But I have a different opinion as follows:
As a matter of fact,code section are shared among
ed processes,so the memory footprint predicate shouldn't hold.
The only reason I can think of is that
is non-threadsafe so that web server can only create subprocesses for each request.
While in fastcgi mode web server can boost up the performance by multiplexing tricks,thus reducing the
overhead.
In a word,the drawback of mod_php is not its memory foot print,but the overhead of
,but if
can be thread_safe,
won't be necessary and this will be the most efficient solution to serve requests.
The above is my opinion,but not 100% sure.
Is that right?
But I have a different opinion as follows:
As a matter of fact,code section are shared among
Code:
fork()
The only reason I can think of is that
Code:
mod_php
While in fastcgi mode web server can boost up the performance by multiplexing tricks,thus reducing the
Code:
fork()
In a word,the drawback of mod_php is not its memory foot print,but the overhead of
Code:
fork()
Code:
mod_php
Code:
fork()
The above is my opinion,but not 100% sure.
Is that right?