On Fri, Jul 4, 2014 at 1:03 AM, Gilles Dubuc <gilles(a)wikimedia.org> wrote: This looks pretty bad. Thanks for calling it out. Thumbnailing improvements are still in the works on our end, and the idea May I ask: what is the range of this radar? Radar signal declines in quality as distance increases, and it is vulnerable to interference from diverse factors, like atmospheric turbulence and birds. Nobody likes sinking time, energy and hardware on an architecture that doesn't work. Even when it's the right thing to do. I think appetite for this work might grow if some there were some definite plans afoot for moving us past it, to a setup that works.

Hi Gilles, On 04 Jul 2014, at 10:03, Gilles Dubuc <gilles(a)wikimedia.org> wrote: Yes, our Swift capacity expansion has completed. Although the capacity expansion had been planned with reduced storage for thumbs in mind for the future, work that hasn’t started yet, we should have space for this available right now and it shouldn’t be problematic provided that we monitor it well. So please go ahead with this for newly uploaded images - we’ll see how it goes. Filippo will look into whether Swift’s TTL feature is usable for us these days; hopefully we can use it to reduce storage of unused thumbs / thumb sizes until we move them out of Swift completely. Yeah. As you know there’s a fair amount of desire to change the way thumb handling & storage works, support more variants (sizes, quality), etc by various teams. I’m starting to think it would be good for us to organise a sprint on this very topic, get the multimedia team, relevant Ops people and some other interested developers from other teams and really dive into these problems. — Mark Bergsma <mark(a)wikimedia.org> Lead Operations Architect Director of Technical Operations Wikimedia Foundation