ruby on rails - background job vs after_save callback -

I have a model called voting which will change many times (people voting on stuff). After voting, I do other analytics, such as voters exchange on men / women, age, etc. This result (adult vote, women's vote etc.) has the same model in updating the counter.

I wonder what is the best way to do this after saving the processing, can it be background work (I'm using the delayed_jobe plugin) or it's the most Should be left good? Which is better than a better performance perspective?

I do not really need to show the other latest data to the user (even after_save does not complete the callback anyway).

Thank you