I'm serving cached version to all anonymous users. I'm kind of using it as a lazy man's varnish drop-in, it works great except it will offer a nice WSOD from time to time, and exclusively for the website.com front page.
I don't know why or when, but it looks like it depends on how busy the site is. The more anon users on the site, the faster the frontpage will wsod.
I've not found any errors in nginx or php logs, http response is 200.
Where in microcache configuration should I start looking?
I'm using Perusio's nginx config, nginx/1.2.5, pressflow6
Or there is no real advantages to use ESI over http://drupal.org/project/cache_warmer? Installation of Cache Warmer looks too complicated, ESI must be easier.
We are working on a commerce site with the following caracteristics:
- We have 4 different roles (anomymous, standard, special and admins).
- We have a shopping cart block visible in all pages (except checkout). This is of course a dynamic block that varies per user, not per role.
- All users and roles can see this shopping cart block (including anonymous, as everybody can order to us).
- The content (markup) displayed in most pages vary per rol.
I've just released a drush command that implements a crawler to keep the cache warm. Although it was developed with microcaching in mind you can use it for keeping any type of external cache warm. Varnish, or whatever type of caching proxy you decide to use.
To keep a cache warm just set a cron job of the command invocation that suits a particular site traffic patterns.
To prime a cache fire the command once with the proper options to get all the desired content in cache.