Re: Caching static images using memcache/nginx

I am not 100% sure. It is better to check it I think it is configurable but I am not sure what is the default behavior. On Thu, Sep 15, 2011 at 9:52 PM, Thomas Weholt wrote: > Aha! That's briliant, but doesn't nginx set those headers for me when > returning a static

Re: Caching static images using memcache/nginx

Aha! That's briliant, but doesn't nginx set those headers for me when returning a static resource like a image? Thomas On Thu, Sep 15, 2011 at 4:52 PM, Ilian Iliev wrote: > How about to set correct headers and make the images cached on user side > instead > of wasting

Re: Caching static images using memcache/nginx

How about to set correct headers and make the images cached on user side instead of wasting memchached resources? If you are serving tons of thumbs multiple times I bet that the traffic will be bigger problem than the time it took for these images to be read from disk. Check this post ->

Re: Caching static images using memcache/nginx

What is your goal in doing this? You are unlikely to see any performance gains from this effort. It won't render any faster for your users. Sending bytes over the network is far slower than reading them off disk, so it's not likely to be a bottleneck in terms of page loading. Your filesystem

Re: Caching static images using memcache/nginx

Good point Cliff! I just assumed serving static content would benefit from caching, but perhaps my effort is more well spent focusing on other aspects of my app right now. Thanks :-) Thomas On Thu, Sep 15, 2011 at 3:42 PM, J. Cliff Dyer wrote: > What is your goal in

Caching static images using memcache/nginx

Ok, this might sound a bit off-topic but bear with me. I got a templatetag in an app that generates thumbnails ( django-photofile ). In my templates it might look like this It will generate a thumbnail of the photo in 100x100 in a folder served by nginx for all static content and return an url