title: Server-side image resizing performance
body: <p>I have been noticing more and more from the big sites (Google, Facebook, Youtube and co) that they are resizing images "close" to their desired measurements client side and I am wondering whether this is a shift in the way people are thinking or them being lazy.</p>
  
  <p>Take a scenario of adding a new image size to a standard set of images at particular sizes for a set of products (e-commerce) which number into the 100's of thousands, maybe millions.</p>
  
  <p>Imagine I have a copy of my original image that is 300x350 or whatever and client side, resize it to 200x250. I do this for each product for 20 products on a page.</p>
  
  <p>Is the work and problems server-side of accomodating this new size really worth the benefit client side?</p>
  
  <p>If not then what is a good way to judge when you should pre-process a certain size?</p>
  
  <p>If yes, is there ever a time where server-side processing and caching might become overkill (i.e. housing 8 images of 110x220, 120x230, 150x190 etc)?</p>