Closed
Bug 964772
Opened 12 years ago
Closed 12 years ago
Cleanup and resizing of infrastructure
Categories
(Webmaker Graveyard :: DevOps, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: johns, Unassigned)
Details
(Whiteboard: [workweek-devops][workweek])
In an effort to save costs, I'd like for us to go through a process of cleanup, resizing, and removal of unneeded assets.
1) Cleanup unused, unneeded buckets
2) Remove old backups of mongodbs
3) Determine if we can resize web nodes, database nodes
4) Determine if we can combine some of the databases into a single staging db.
Comment 1•12 years ago
|
||
Also, maybe switch to the m3 nodes? I believe those are cheaper than m1's now, right?
Whiteboard: [workweek-devops]
Updated•12 years ago
|
Whiteboard: [workweek-devops] → [workweek-devops][workweek]
| Reporter | ||
Comment 2•12 years ago
|
||
We did the following:
1) Combined all webmaker app staging databases into a single RDS instance, deleted 5 RDS instances
2) Cleaned up old cruft and lingering nodes that we not being used
3) Moved all staging clusters to us-east-1b, where we had 13 available reserved m1.medium instances.
4) Resized all RDS databases overnight last night based on their utilization.
This has netted us approximately a 25% price drop. We had been running about 20-21 dollars an hour, and we are now averaging 15 an hour. This will save us about $45,000 a year.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•