Gearman is a great tool for farmed or distributed work. It's some kind of basic cloud handling: Many Worker processes (usually running on many different servers) are waiting for jobs to process and there's (hopefully) always another worker taking over if one worker (server) should ever die. But what happens, if a single job dies and should be repeated?
Statistics are nice, but may also increase database load. Counting web users (page impressions) may produce a lot of UPDATE requests setting counter=counter+1. I tried to merge them using Gearman.
I wrote about Gearman some time ago and didn't get the tuits to write the next posts, but here we go: How to start working with Gearman.
I strongly suggest that you don't start by adding Gearman to your productional systems because there are many things to consider and you probably don't want to rewrite everything once it's running.