Closed Bug 1567257 Opened 5 years ago Closed 5 years ago

Database changes to increase IOPS cap

Categories

(Tree Management :: Treeherder: Infrastructure, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: armenzg)

References

Details

Attachments

(2 files)

We want to try to increase the IOPS cap of the treeherder-prod database by increasing its database size instead of switching to the Provisioned IOPS storage. The latter is far more expensive (about $1,000/month difference for 1TB).

Increasing the storage size to increase the IOPS cap might just be sufficient.

Let's give it a try!

Attachment #9079124 - Flags: review?(jwatkins)

Increasing the storage size is a fine alternative in this situation but I want everyone to beware we cannot downsize rds storage cap once it has been scaled up. So this change will be permanent on the prod instance.

Attachment #9079124 - Flags: review?(jwatkins) → review+

Go for it. Thanks!

-dev has completed and is now rolled back to gp2. -prod-ro is still modifying

Mon, 22 Jul 2019 16:15:02 GMT Preparing for modification of storage
Mon, 22 Jul 2019 16:16:05 GMT Finished preparing for modification of storage
Mon, 22 Jul 2019 16:16:20 GMT DB instance shutdown

-prod-ro has completed
Mon, 22 Jul 2019 16:16:03 GMT Applying modification to allocated storage
Mon, 22 Jul 2019 20:35:19 GMT Finished applying modification to allocated storage

-prod storage cap increase started

Tue, 23 Jul 2019 15:58:30 GMT Applying modification to allocated storage

This graph shows that we're using above 3,000 IOPS.

Let's hope this was it! Thanks Jake!

Status: NEW → RESOLVED
Type: defect → task
Closed: 5 years ago
Resolution: --- → FIXED

For the -prod record:
Tue, 23 Jul 2019 15:58:30 GMT Applying modification to allocated storage
Tue, 23 Jul 2019 18:34:45 GMT Finished applying modification to allocated storage

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: