41–50 of 59 posts
Earlier quoted context omitted.
Well without some sort of caching, his site very well could fall over when being on the front page of something like HN. Putting Varnish in front a site, even with something simple like a 1 minute cache on everything, makes you pretty much immune from having "large amounts of traffic" being a real problem.
Exactly, thanks frank! :P
I feel like I am missing something.
Earlier quoted context omitted.
If all you need is crop or resize, might as well use nginx in my opinion.
There was one annoyance we have to fix that I don't think the nginx module supports & that's rotating images based on their exif orientation (mobile devices love to upload landscape images w/ an exif-orientation in portrait). Python is definitely an OK solution for this as it turns out. We resize a few million of images a day on-demand on two n1-highcpu-8 GCE instances. Although, they could easily be a fourth the siz…
I wrote a similar article a few years back that employs Lua and imagemagick bindings: http://leafo.net/posts/creating_an_image_server.html
If you use a CDN such as Cloudflare, you can do a similar trick but forget about the proxy cache (and associated storage needs) - as long as every image at every size gets a unique URL and you control http cache headers correctly, Cloudflare will store copies of every image size ever requested across their CDN network. In terms of this blog post, you'll only need the "resizing server". This is a very simple and state…
That's not quite true. Cloudflare (like virtually every CDN) only caches files at the edge server that handled the request. And they purge the files after a short period of time--even if your cache-control headers ask for a longer time. Most won't tell you how short (including Cloudflare), but some CDNs will delete files after as little as two hours.. 24 hours is very common. Most CDNs also give you no visibility abo…
How many of those same people are now going on about how nginx has finally got some support for loadable modules and built in processing like this?
A few years ago everyone was jumping on nginx saying it's the 2nd coming of Jesus and that being a simple web server without dynamic config or modules to do processing made it better than Apache because it's "fast". How many of those same people are now going on about how nginx has finally got some support for loadable modules and built in processing like this?
Earlier quoted context omitted.
Exactly, thanks frank! :P
By removing varnish aren't you now exposed to that risk once again? I feel like I am missing something.
He's basically just moving functionality from Varnish to nginx and thus simplifying his stack a bit.
Earlier quoted context omitted.
Exactly, thanks frank! :P
By removing varnish aren't you now exposed to that risk once again? I feel like I am missing something.