Didn't remember that discussion, sorry. Sounds good. Once we have a separate DB server, we can even run the stats cron jobs from a different (non-web) server, so it doesn't slow down the serving of requests.

I agree that this is fine as an interim solution, was just trying to give a realistic benchmark of it being run on the central server's current data, in case that was helpful.