This past weekend, YackTrack was undergoing some fairly routine database maintenance. This maintenance was not officially announced as it was not supposed to truly affect any site performance. There was a note posted on Twitter in case there was a slight slowdown, but none was really expected. That is, nothing bad was expected until the maintenance was started. Most of the maintenance went smoothly, as is expected for a majority of the work. However, there is always something that changes plans.
One part of the maintenance was running ridiculously slow. At first, I thought it was just taking a bit of time to complete the maintenance, but I noticed that the site was being affected. As I assessed the situation, performance on the site was getting worse. About the same time as I decided to take YackTrack down during the maintenance, the site became unresponsive (how convenient). Once the site was down, I was able to figure out the reason for the slow running maintenance.
What was the real problem? I was trying to cut corners, as most people do for simple things like routine database maintenance. I was trying to implement some performance enhancements, and I figured that some other maintenance could wait until next weekend. If I had thought things through, and did not try to quickly implement my changes, I would have seen that the performance improvements really required some other maintenance. Specifically, I would have seen that the maintenance I postponed until next weekend was really required for my performance improvements. So, I corrected the situation by completing the basic maintenance that I hoped to postpone and then implemented the performance improvements, which ran much quicker this time.
The moral of the story is, there is no such thing as a quick fix and do not try to cut corners when you know better. The database maintenance that I was trying to postpone only required 15 minutes to complete. The performance improvements then required another 30 minutes. However, I wasted almost 5 hours trying to cut corners, and I had to take the site down for a few hours as well.
Again, I apologize for the downtime, the lack of communication prior to the maintenance and for any inconvenience this may have caused. In the future, I will be writing a short blog post to notify everyone of any maintenance, and trying to ensure I do not cut any corners.



![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e5eedc1c-15cc-465e-aa96-05f4ff320021)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=7f9cb3cb-ac3f-4e5e-a951-04d62bc26e12)