Nginx has a bad rep in some ways since the original documentation was in Russian ;). But there are tons of English tutorials, and an English set of docs - especially when it concerns using Nginx as a reverse proxy. If you want I can throw up a tutorial on the topic of Nginx - using it as a reverse proxy (or alternatively lighttpd - I do like Nginx a bit more though) should be a fairly standard practice when Apache is working in a memory restricted environment. The setup is pretty easy once you get the hang of it - the only real problem is getting to know Nginx's config options if you've spent your life knee deep in Apache's ;). The format is different and not INI style.
Nginx only gets as complex as Apache when you want to skip Apache completely and use Nginx as your sole HTTP server. I think 6MB seems a fair initial target. I have no doubt a more complex application will demand additional resources, but a content serving app with little processing would fit the 6MB bill or thereabouts. I'd hazard Wordpress' average is similar once its caching is enabled. Best regards, Paddy mothmenace wrote: > > Wow Thanks a million Padraic, You explained the httpd process very nicely > and I'm much clearer on what's going on now. I will try some of the > optimisations you mentioned to see if I can find the best level. The Nginx > sounds quite advanced but I really like the concept. > > Also, thanks for confirming that 6mb is a reasonable amount of memory for > a web app! > ----- Pádraic Brady Blog: http://blog.astrumfutura.com Free Zend Framework Book: http://www.survivethedeepend.com OpenID Europe Foundation - Irish Representative -- View this message in context: http://www.nabble.com/ZF---Memory-usage-tp20678541p21309088.html Sent from the Zend Framework mailing list archive at Nabble.com.
