News for hackers. Stuff that matters.
Re:How Imgix Built a Stack to Serve 100k Images per Second by ddorian43 on Monday August 31, 2015 @05:43AM (#10146084)
2 ways to do thumbnails. 1 Precompute(what they did) and 2 Compute on demand(imgix)

Of course the best is to do something in the middle.

Re:How Imgix Built a Stack to Serve 100k Images per Second by jawngee on Monday August 31, 2015 @06:43AM (#10146205)
Imgix is the middle, they process the parameters once and cache the result.
Re:How Imgix Built a Stack to Serve 100k Images per Second by ddorian43 on Monday August 31, 2015 @06:52AM (#10146224)
That is just caching.

Middle is: You precompute some fixed presets(like him, lower latency) but also have the ability to generate on demand if a preset doesn't exist(used when adding new presets, no reason to wait *days to have the new preset).

Re:How Imgix Built a Stack to Serve 100k Images per Second by skuhn on Monday August 31, 2015 @03:10PM (#10148485)
Once you've built a system that works fast enough to handle image rendering work on-demand, then adding batch or precomputational features is largely just creating requester logic to ask for the image before the real demand arrives.
Re:How Imgix Built a Stack to Serve 100k Images per Second by boundlessdreamz on Monday August 31, 2015 @05:50AM (#10146097)
Yes. But why should Precompute take a few days?
Re:How Imgix Built a Stack to Serve 100k Images per Second by Rifu on Monday August 31, 2015 @06:06AM (#10146125)
Perhaps they have a few million images to go through.
Re:How Imgix Built a Stack to Serve 100k Images per Second by boundlessdreamz on Monday August 31, 2015 @06:43AM (#10146200)
Ah. I think you are right. Misread the original post. They want to process "existing media". I was thinking of "new media".