3 ms·
FPM is stuck with the overhead of latency and IPC delay from its CGI legacy. Litespeed threw all that out with their approach to PHP, it's far more lightweight
by ck2 14y ago
FPM is stuck with the overhead of latency and IPC delay from its CGI legacy.
Litespeed threw all that out with their approach to PHP, it's far more lightweight and why it's so much faster.
I really hope that someday, someone will sponsor a module for a FPM replacement inside nginx like Automattic did for spdy and CloudBees/Apcera did for websockets.
Given the sheer number of PHP and nginx users, you'd think this would have happened even before spdy or websockets but maybe the impression is php-fpm is "good enough".
- nodesocket 14y agoWhat are the performances differences between using LSAPI and FPM. Are we talking > 10%? If so, it does seem strange there has not been a nginx module developed?
- deleted 14y ago[deleted]
- FooBarWidget 14y agoThere is one. It's called Phusion Passenger (https://www.phusionpassenger.com https://www.phusionpassenger.com). At this time it supports Ruby and Python. More languages are planned.
- fooyc 14y agoFPM is a FastCGI server. That is, it does socket-based IPC (TCP or unix), with a binary protocol (FastCGI), with one process per request. Litespeed seems very close to that: socket based IPC, with a seemingly custom binary protocol, one process per request. Could you tell what's better in Litespeed module ?