These are my links for 17 nov 2011 from 23:06 to 23:56:
- Optimizing WordPress with Nginx, Varnish, APC, W3 Total Cache, and Amazon S3 (With Benchmarks) | danielmiessler.com – So I’ve spent the last couple of weeks tweaking my web server stack. I like my site to pop, and I’ve finally achieved a configuration that I’m somewhat happy with.
In sum, I’m running Varnish as a front-end to Nginx which is running WordPress loaded with the W3-Total-Cache plugin. The W3-Total-Cache plugin is configured to use both memcached as well as Amazon S3 as its CDN. All of this sits on Ubuntu Linux with Linode as my host.
- A Varnish Primer | danielmiessler.com – Despite the title, this article has nothing to do with painting. Here I'm going to talk a bit about the Varnish Cache — a web application accelerator designed to dramatically improve how quickly your website loads. Varnish works by caching and serving as much content as possible as "static", including dynamic results, e.g. blog posts from a CMS like WordPress.
- Varnish best practices « Kristian Lyngstol’s Blog – A while ago I wrote about common Varnish issues, and I think it’s time for an updated version. This time, I’ve decided to include a few somewhat uncommon issues that, if set, can be difficult to spot or track down. A sort of pitfall-avoidance, if you will. I’ll add a little summary with parameters and such at the end.
- Cain Manor | Setup logging for Varnish – So far, we’ve got Varnish installed and have a correct default.vcl. Now let’s make sure AWStats/JAWStats can read them.
[Or http://www.hping.org/visitors/ 😉 😉 ]