Even tho I love Lighty, it has a few known short-comings, mem leak when under heavy load in a reverse proxy setup is one of them. Old reported bug that dont seem to be fixed any time soon.. Might very well be due to the fact that they are now in the process of doing a total rewrite for the 2.0 release, or that not many use it in such a setup?

In any case, till this is resolved Ive had to look into alternatives for the task. I heard alot of good from my friends in Russia about Nginx, but at the time the documentation where pretty much solely in Russian.
This has improved(Nginx Unofficial Wiki) alot over the last year, so last night it was again time to dust off the VE I had setup months ago and give it another go.

After a few curse & spit rounds with rewrite rules & deciding to redo the conf layouts, I had a working setup, only SSL was acting up. This morning I saw what I had done, or what I didnt do I should say. Since I redid the entire conf setup I had missed out the include of the proxy.conf in the SSL server settings. *sigh*

I will be adding Varnish to the pie later, more on that when time permits.
Check the wiki for info on the above, will add to it later tonight.

The setup & configuration of Nginx were really nice, it hogs so little mem & cpu time its almost like its not even running… Really! I still have Lighty & Apache on the backends tho, but many of them might very well be replaced with Nginx..

ура товарищей !

Tags: , , , , ,

rss feed for comments| Both comments and pings are currently closed.

One Response to “Step back Lighty, jump forward Nginx”

  1. Rantville » Blog Archive » I Va(r)nish, did you notice? Says:

    […] an earlier post I told you how Lighty got replaced with Nginx for the reverse proxy duties. At the time I had […]