Closed Bug 1382207 Opened 8 years ago Closed 8 years ago

Reduce production DB size

Categories

(Webtools Graveyard :: Pontoon, enhancement, P2)

Product:
Webtools Graveyard
Component:
Pontoon
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mathjazz, Assigned: mathjazz)

References

Details

As a side effect of bug 1380349, we discovered that the production DB contains a lot of unused data, possibly bloat: https://devcenter.heroku.com/articles/managing-vacuum-on-heroku-postgres#determining-bloat. At the time of running the test, 1.39 GB. The total DB Data Size was 4.24 GB. As it turned out on the staging server, removing this data speeds some DB queries up quite noticeably (up to 40%). We should try to VACUUM the DB tables first to eliminate the bloat. If that won't be sufficient, we should create a new instance and remove the old one. The latter will require the production site to be in the maintenance mode for 3-5 minutes.
Vacuumed. DB size remains unchanged, probably because of the empty rows. We should backup and restore to bring the size down.
DB backed up and restored. DB size decreased from 4.78 GB to 3.63 GB.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.