Comments on: NginX as a caching reverse proxy for PHP http://blog.killtheradio.net/technology/nginx-as-a-caching-reverse-proxy-for-php/ or die trying Fri, 23 Jul 2010 17:30:09 +0000 hourly 1 http://wordpress.org/?v=3.0 By: caching-dynamic-content-using-nginx | DeDiHosting - Blog.samp-online.com http://blog.killtheradio.net/technology/nginx-as-a-caching-reverse-proxy-for-php/#comment-1472 caching-dynamic-content-using-nginx | DeDiHosting - Blog.samp-online.com Mon, 31 May 2010 21:12:11 +0000 http://blog.killtheradio.net/?p=394#comment-1472 [...] another bookmark Kommentare [...] [...] another bookmark Kommentare [...]

]]> By: HAProxy’s keep-alive functionality (and how it can speed up your site) | kill the radio http://blog.killtheradio.net/technology/nginx-as-a-caching-reverse-proxy-for-php/#comment-1445 HAProxy’s keep-alive functionality (and how it can speed up your site) | kill the radio Tue, 11 May 2010 02:33:38 +0000 http://blog.killtheradio.net/?p=394#comment-1445 [...] while back I wrote a post about using NginX as a reverse-proxy cache for PHP (or whatever your backend is) and mentioned how I was using HAProxy to load balance. the main [...] [...] while back I wrote a post about using NginX as a reverse-proxy cache for PHP (or whatever your backend is) and mentioned how I was using HAProxy to load balance. the main [...]

]]> By: Andrew Lyon http://blog.killtheradio.net/technology/nginx-as-a-caching-reverse-proxy-for-php/#comment-1364 Andrew Lyon Fri, 05 Feb 2010 21:02:03 +0000 http://blog.killtheradio.net/?p=394#comment-1364 That makes sense. I haven't looked at the keepalive stuff in HAProxy, I'll check it out though. After doing some benchmarks with and without HAproxy, I'm convinced that having it slows down the request by about as much as adding a millimeter to the length of the network cable connecting the request to the machine. It's almost like it isn't there. Add the features and speed of NginX, plus the fact that it can do its own caching, and that's a setup which for how insanely fast it is, really isn't that complicated or high maintenance. Also really good for a lower-power server or VPS. Thanks for the comment! That makes sense. I haven’t looked at the keepalive stuff in HAProxy, I’ll check it out though. After doing some benchmarks with and without HAproxy, I’m convinced that having it slows down the request by about as much as adding a millimeter to the length of the network cable connecting the request to the machine. It’s almost like it isn’t there. Add the features and speed of NginX, plus the fact that it can do its own caching, and that’s a setup which for how insanely fast it is, really isn’t that complicated or high maintenance. Also really good for a lower-power server or VPS.

Thanks for the comment!

]]> By: Willy Tarreau http://blog.killtheradio.net/technology/nginx-as-a-caching-reverse-proxy-for-php/#comment-1363 Willy Tarreau Fri, 05 Feb 2010 06:11:05 +0000 http://blog.killtheradio.net/?p=394#comment-1363 It seems to be the architecture more and more people are converging to, and this will be especially true with keep-alive support in haproxy 1.4, because people won't have to trade between availability and site load time for high latency users. Also nginx+haproxy work reliably and very fast together. Both can take advantage of each other's optimisations to save CPU and network bandwidth. I'm aware of a very large site in the range of the million concurrent visitors making use of both. It would most likely not work if any of the two components were to be replaced. It seems to be the architecture more and more people are converging to, and this will be especially true with keep-alive support in haproxy 1.4, because people won’t have to trade between availability and site load time for high latency users. Also nginx+haproxy work reliably and very fast together. Both can take advantage of each other’s optimisations to save CPU and network bandwidth. I’m aware of a very large site in the range of the million concurrent visitors making use of both. It would most likely not work if any of the two components were to be replaced.

]]>