whats the total number of hs in:
q: nginx proxy_cache or memcached i currently use nginxs proxy_cache for file-based caching in front of three django applications (apache/mod_wsgi). for some locations/urls, i disabled proxy_cache and used memcached (per view) within the django app instead. now i wonder whether pointing nginx to memcached is more efficient.
i read here, that nginx can serve pages from memcached – but does django write complete pages to memcached when configured for per view caching (and does it set an expiration date according to the @cache_page parameter)?

a: using different applications to write to and read from the cache is always difficult even when there are are highly prescribed data formats/protocols. in this case, while both nginx and django can access memcached, its very unlikely they will use the same data/indexing formats.
reverse proxy caching is a very different beast from origin server caching. realy it makes no sense to do any output caching at the application tier (its often a good idea to do data caching here though). all the content which will be sent out via http should be cached by nginx, and only by nginx. what substrate it uses for that is a different question. 

user
There are 49 "h"s in the text you provided.
assistant