my understanding was that fastcgi is faster because uses persistent processes (http://en.wikipedia.org/wiki/FastCGI). It is faster than mod_php because it doesn't have to build and destroy processes as they come.
If you are looking at making the switch, perhaps you should investigate nginx. It has a similar serving model like fastcgi, using php-fpm, and its smaller memory footprint makes it appealing.

http://wiki.nginx.org/Drupal

Eric

On Mon, Dec 15, 2014 at 11:57 AM, Todd Millecam <tyggna@gmail.com> wrote:
FastCGI is faster than mod_* in general, unless you're a python shop, then wsgi is probably better.  It looks like the php-equivalent project is php-fpm.

FastCGI is highly optimized C-code specific to dishing out dynamic web requests.
mod_php is just the php interpreter embedded into apache.

Another nice thing about FastCGI is it lets you spawn/control multiple worker threads, so it tends to be better for scaling-out your app, and you can redirect traffic to workers that aren't necessarily on localhost and use apache as a faux load-balancing solution.

On Mon, Dec 15, 2014 at 11:25 AM, Keith Smith <techlists@phpcoderusa.com> wrote:


Hi,

I am being told by our data center that FastCGI is less resource intensive than mod_php.  I am being told this will help with the load put on the server by Drupal.

Any thoughts on this?

Thanks in advance!!

Keith

--
Keith Smith
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


--
Todd Millecam

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss