Our Results development team has spent the past few months building a brand-spankin' new product to replace the old one. And in order for this brand-spankin' new product to work properly, we need to move data into it from the old database. Well, they decided to add a little liveliness to an otherwise boring exercise which can be witnessed below:
results.active.com is our hub for communicating race results to people. We train event timers on how to use the backend portion of the system, and after a given race is completed the timers upload results, making them available to the world at large.
We typically see a lot of traffic on results.active.com after large events, such as the Marine Corps Marathon or the Chicago Marathon. And to be fair, results.active.com hasn't had an exemplary performance record when it comes to handling the volume spikes we get on the Monday after major events.
We've just released a major update to results.active.com adding 3X the scalability we had before. We've also made tweaks to the architecture so that we can add additional servers to the load-balancer should we get any unanticipated increases in volume.
So if you see any issues with site responsiveness please let me know (here on this blog) and I'll look to it personally and immediately.