I have an application that runs well using lighttpd with PHP. In an effort
to reduce the memory footprint I tried porting it to the busybox ( 1.20.1 )
httpd. It was easy to get this working and it seems to work properly. What
isn't good enough is performance when executing PHP scripts. It looks like
the httpd is using fork/exec for each cgi, and that fork/exec can use a lot
of CPU. There might also be some downsides to repeated alloc/free in the
embedded environment. By comparison, lighttpd starts a programmable number
of php-cgi processes at startup, then keeps them around and just feeds
scripts to them as needed. It is feasible to go back to lighttpd but before
giving up for this reason, I wanted to ask if my understanding or build of
the httpd is incorrect in some way. Any thoughts, suggestions, comments ?

George


_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to