All you need to know about FastCGI Process Manager (FPM)

[@iangrant4756]

As no one seems to have explained how to pronounce “Apache”… it’s pronounced hard-“a patch ee”. So, ah-patchy! The e at the end is stated because it’s not an Anglicized name, but is the original name of a Native American population. For the Apache project, the name was settled on well before any of the awareness about such things became prominent. It was originally “a patchy” service, which (quickly) gave rise to the name.

[@Mediatomcat]

Thanks. was driving me crazy. 😂

[@SpencerTaylorOnline]

This is an excellent video. Thank you for taking the time to explain the FPM configuration.

[@DavidLopez-gs1fb]

Thanks from Colombia, South America. Pretty useful.

[@davidmenache]

This was helpful thank you. Look forward to seeing more content. Btw, I've never heard Apache pronounced like that. For whatever reason it got my attention. I'm pretty sure the name Apache comes from the phrase "A patchy" piece of software. ...or something like that anyway. It wouldnt surprise me at all if it's already been discussed at length somewhere below. Going forward, whenever I see that word Apache, I will now think. Dan Persson explaining fcgi and A-pash! :). Maybe you can do a followup to this on how to configure multiple vhosts with various phps and confs. Cheers!

[@SpencerTaylorOnline]

For non-native English speakers, Apache is not an intuitive word to pronounce. The name comes from the Native American Apache tribe and is unrelated to "a patchy." During the 19th century, when America was waging war on the Indian Nation, the Apache were known as fierce warriors. The Apache was also one of the first Native American tribes to master riding horses for hunting buffalo (horses were not native to North or South America ) and later fought the American soldiers and other people who tried to eliminate them. The idea behind the Apache server name was that it was fast like the Apache Indians were. I won't determine whether it was a good use of the tribe's identity, but that's a somewhat lengthy explanation for its etymology. Apache can easily be mistaken for a French name or word, so I think I understand why he pronounces it this way.

[@marerkkbiker]

Great content, diving into topic without bs. Thanks! Subscribed

[@cetx]

Great explanation of FPM.

[@jelajahmania]

how to optimize php fpm for 10000 req per sec , with nginx,mysql,laravel

[@DanielPersson]

Hi la212hd Not sure how you can optimize anything using Laravel. But my suggestion would be to benchmark it and then do iterative changes to improve the code. FPM and native module isn't that different. The improvements you get with FPM is a separate process where you can manage memory better and get an improved compute speed if you run multiple processes at the same time. But usually the problem is your implementation not using efficient code. I hope this helps. Best regards Daniel

[@WhiteSiroi]

thank you D, very helpful

[@kenjohnsiosan9707]

Where or what do I need to study to have a better understanding of the module and other Apache PHP-related stuff? Thank you, sir.

[@DanielPersson]

Hi Ken Thank you for watching my videos. Hard for me to know exactly what you are looking for from the question. A great resource to read to learn more of the PHP language is the documentation. The community spends a lot of time to work on it and it's pretty good. If you want a more structure course I could recommend this for a beginner. imp.i384100.net/m5OvK1 I hope this helps. Best regards Daniel

[@It_guy613]

i recommend the Michigan course as well but for the documentation i personally don't think that it is very friendly for beginners(being a beginner myself) since in most of the examples they use functions that you should at least have a better grasp of php basics and structure to better understand what it's about. i have been using php for a few months and i still find it very difficult to read the documentation, but that is just my point of view, if you feel like trying i'd totally encourage you, maybe that is just me.

[@marthetra7593]

hello Thanks Can you help me to understand what the master php-fpm process is for. is it possible that a php-fpm process executes this command "bash sh -c id"?

[@DanielPersson]

Hi Marthe The easy explanation is that before you ran it with the Apache server as a plugin so the Apache services needed to be scaled appropriately and handle all the load of both complex processes. As PHP programming gets more complex with more processes, it's beneficial to break it out. So now, when Apache wants to show a PHP page, it will call FPM to render the page as a separate process. This means that FPM can be scaled after demand, and Apache can focus on routing traffic as indented. I hope this helps. Thank you for watching my video. Best regards Daniel

[@josuaschmid501]

I would have found interesting if the video would have at least scratched the surface of the difference between apache handler and FastCGI.

[@yaroslavhoncharuk6031]

thanks

[@LinhNguyen-bp9hd]

so this is the reason why FPM is considered to be faster than mod_php and has become a standard way of deploying php app?

[@DanielPersson]

Hi Linh My understanding is that they have separated call concerns by creating a service that you can scale separately. And there is nothing that hinders you from setting up multiple FPM services in like a Kubernetes kluster to scale up and down the compute power behind you web server. The FPM service have been default in nginx longer than apache but I think this is a step in the right direction. Thank you for watching my videos. Best regards Daniel

[@chandrajithchandrajith6446]

❤❤

[@mehdi-vl5nn]

so fpm is per fork ?how is that related to MPM Apache side

[@DanielPersson]

Hi Mehdi. FPM is a service apache calls. Never used MPM so I don't know how they stack up. Thank you for watching my videos. Best regards Daniel

[@syafiqsafiyan5194]

10years i pronouce “Apache” is Wrong 😅..

[@electroplank587]

sorry pal but you're pronouncing apache wrong and it's irritating

[@vivekkadam748]

Why I read this comment 😭