Closed Bug 726739 Opened 12 years ago Closed 12 years ago

caching node for QMO in AMS1

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nmaul, Assigned: bburton)

References

(
URL
)

Details

+++ This bug was initially created as a clone of Bug #723591 +++

Once QMO is moved to genericrhel6 in PHX1, we should consider caching it in AMS1 for EU performance.

For this to be really feasible, it must first gain WP Super Cache, so that sends proper cache headers for content... currently non seem to be sent, which will result in a 0% hit rate and generate lots of unnecessary round-trips back to PHX1.

Once that's done, it also becomes feasible to host static content on a CDN... WP Super Cache makes this relatively painless as well.
Assignee: server-ops → bburton
Move to PHX and upgrades to generic cluster should be sufficient for now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.