A different take on "worker mode": the Qbix webserver

[gggeek]

Today I read about Qbix, (yet another) "app server for php".

It is a pure-php application, which claims to be able to achieve both excellent speed, low memory usage and great stability by (afaict):

1. loading php classes and doing app. state set-up in the "main process"
2. for each incoming request, forking the "main process" into a new "worker process" which will handle it

The stability part is guaranteed by having 1 worker process per request - no memory leaks out of the box.
The speedup and reduced memory consumption comes from having the worker processes being forked after having the php classes already in memory (and possibly the connections to external services such as DBs open).

While I have not even tried to run it even once, it seems that this might be a good execution model, if not in general, at least for a specific set of php applications, eg. those that take care of routing on their own and are distributed as containers, where there is no need to reload state in case of live changes to the php code.

Can anyone comment on the pros/cons of this vs. the FrankenPHP worker mode?