title: background job vs after_save callback
body: <p>I have a model called Vote that gets changed very frequently (people voting on stuff). I do other analytics after a vote is save, such as interpolating if the voter is male/female, what age etc. This results in updating counters in (adult votes, women votes etc) the same model. </p>
  
  <p>I wonder what's the best way to do this after save processing, should this be a background job (I use delayed_job plugin) or should this be best left as an after_save callback? Which is better also from performance standpoint? </p>
  
  <p>I don't really need to show upto the second latest data to the user (even the after_save callback doesn't accomplish that anyway).</p>
  
  <p>Thanks</p>