Closed
Bug 1174852
Opened 10 years ago
Closed 10 years ago
Gzip application/atom+xml response of feed XML
Categories
(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)
Infrastructure & Operations Graveyard
WebOps: Community Platform
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jezdez, Assigned: cliang)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1346] )
Seems like https://developer.mozilla.org/en-US/docs/feeds/<format>/revisions (e.g. https://developer.mozilla.org/en-US/docs/feeds/atom/revisions) isn't been being gzip'ed which would result in far less network traffic. E.g. right now the revision feed for en-US is ~4MB and could be compressed to ~161kb with highest gzip setting.
| Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(cliang)
| Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-webops → cliang
Flags: needinfo?(cliang)
| Assignee | ||
Comment 1•10 years ago
|
||
For the stage environment, I've added application/atom+xml to the list of MIME-types that the load balancer will deliver as compressed. In testing, it looked like it added a little under a second of processing time on the initial load of the file; the file is then cached, making subsequent access fairly quick.
@jezdez - Can you verify that this works as intended before I apply the same change to production?
| Reporter | ||
Comment 2•10 years ago
|
||
@cyliang Yeah that works as expected, the feed on stage only transfers ~70kb and prod ~600kb with similar endresults once unpacked. Let's apply that to prod as well. Thanks!
| Assignee | ||
Comment 3•10 years ago
|
||
I applied the change to production and cleared the cached atom feeds from the load balancers (to help force them to be compressed). Keeping this open a few days to see if there are any unanticipated negative side effects.
| Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•