Database Troubles
This morning we had some database problems. With help from Engine Yard we were able to identify the slower queries and eliminate them. Here you can see our database exploding:…
This morning we had some database problems. With help from Engine Yard we were able to identify the slower queries and eliminate them.
Here you can see our database exploding:
img http://img.skitch.com/20090130-x5dfywbure73aqfjt3bqspckf3.png
And the sweet release when we deployed the fix:
img http://img.skitch.com/20090130-rkcn1b4d566f2x226f46deuq3.png
Basically, our events
table has swelled to over 30m rows taking up 18gb of disk space. We have some solid indexes in place, but saving new events and querying are both becoming problems. As we plan to do more fancy things with the dashboard in the future this needs to be addressed.
Currently the plan is twofold:
-
Split
events
table intoevents
andevents_archive
. Older events will go intoevents_archive
, archiving will happen nightly on a cron. This will dramatically reduce the size of theevents
table. -
Re-evaluate every query that touches
events
, make sure it’s using the best possible index.
We’ll update you as we make progress. Thanks!
Written by
Related posts

GitHub Availability Report: September 2025
In September, we experienced three incidents that resulted in degraded performance across GitHub services.

The developer role is evolving. Here’s how to stay ahead.
AI is changing how software gets built. Explore the skills you need to keep up and stand out.

How GitHub protects developers from copyright enforcement overreach
Why the U.S. Supreme Court case Cox v. Sony matters for developers and sharing updates to our Transparency Center and Acceptable Use Policies.