Topic: Why is it recommended to use fcgid ?

[mrdj1024]

i use php 8.1 running as apache module,why is it recommended to use fcgid?
im not overly sure the pros and cons of making the switch,but i will if its needed to keep things up to date.

[Steffen]

FCGI(mod_fcgid) memory usage of Apache is less en the Speed is on par when running as module. There are advantages to running PHP with FCGI. Separating the PHP code from the web server removes 'bloat' from the main server, and improves the performance of non-PHP requests. Secondly, having one permanent PHP process as opposed to one per apache process means that shared resources like persistent MySQL connections are used more efficiently. And maybe even more important is stability, since I run FCGI my server never crashed primarily caused by php (extension) errors and out of memory errors.

Also with mod_fcgid you can run multiple times with different PHP-versions.

Our moderator James Blond is the mod_fcgid specialist ! He can mention maybe more advantages.

[mrdj1024]

which modules do i need loaded in httpd.conf for mod fcgid to work?
i also use strict transport security and the url rewrite to https.
so most of my changes i make are in the ssl.conf and not the vhost field.
would i need to add the fcgid configuration parameters to my ssl.conf file?
i also use mod evasive,is that compatible with fcgid?

[James Blond]

You only need to download mod_fcgid from the Downloads page from AL. Load the module in httpd.conf
And configure it global or in each vhost.

It would be a hassle to paste all the code here. We have a tutorial how to use mod_fcgid https://www.apachelounge.com/viewtopic.php?t=2394

If you still have a question please ask again.

[Otomatic]

Hi,

This is how I use the FCGI mode with Wampserver.

- Where are installed the different PHP versions
e:\wamp64\bin\php\php7.4.33\
e:\wamp64\bin\php\php8.0.18\
...
e:\wamp64\bin\php\php8.2.6\

- Modifications of httpd.conf file (added lines)

[James Blond]

@Otomatic

You should really take a look at mod_macro https://httpd.apache.org/docs/trunk/mod/mod_macro.html

[Otomatic]

Hi,

Thank you. I already use mod_macro, but for personal use, not for Wampserver.
Wampserver is a development server although some use it as a production server.
To learn, it is necessary to be able to see the results of the actions done.
However, mod_macro generates "virtual" results and that's why, with Wampserver, the options to create, add, modify VirtualHost give concrete and visible results in the httpd-vhosts.conf, httpd-ssl.conf or httpd.conf files.

This could be the subject of a new thread.

[Jan-E]

There is a downside to using mod_fcgid. If PHP crashes before it could produce any output the user will be confronted with an error 500: "end of script output before headers". With PHP loaded through mod_php + mpm_winnt Apache will crash together with PHP. But in my experience the user will hardly notice it because Apache will be relaunched by the other httpd.exe process and try to run the PHP-script again. On my production server PHP 8.1 occasionally crashes with an OPcache error. A crash in PHP with mod_php will lead to a slower response but not to a fatal error 500.

On a Drupal 9 site OPcache is heavily used with a cache hit rate above 99.5%:

[dpat99]

[Jan-E]

These are just the general OPcache stats. I know they are for the Drupal 9 site, because PHP 8.1 only serves that site. Distance is not really an issue. Low traffic, Dutch users, Dutch server. The first user after a restart will notice some delay, but no Errors 500 anymore since I switched from mod_fcgid to mod_php.

[mrdj1024]

finally made the switch to http/2 and fcgid!
noticed less memory consumption when running php scripts
here are the values in my httpd.conf file