Closed Bug 1510354 Opened 7 years ago Closed 6 years ago

Run Balrog behind a CDN

Categories

(Cloud Services :: Operations: Miscellaneous, task)

Product:
Cloud Services
Component:
Operations: Miscellaneous
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: catlee, Assigned: oremj)

Details

We think we can drastically reduce the number of Balrog nodes required to service load by putting a CDN in front of the application. The current responses indicate that we're using a 90s cache: Cache-Control: public, max-age=90
Assignee: nobody → oremj
Finally getting chance to look at this. We wouldn't be able to make this change until 2019 and Balrog is scheduled to move to GCP Q2/2019, do we want to hold off or proceed with this?
Yes, that's fine to hold off. We think we have a few hundred thousand unique URLs in any given five minute window. Would that be a problem for the CDNs?
Nope, there shouldn't be any issue with the number of unique URLs.

Balrog is now running behind Cloudfront.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.