Closed Bug 983815 Opened 9 years ago Closed 9 years ago

Use CDN for homepage/category/search API responses

Categories

(Marketplace Graveyard :: Consumer Pages, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2014-04-01

People

(Reporter: cvan, Assigned: cvan)

References

Details

(Keywords: perf, Whiteboard: [qa-])

We should use the CDN for the following API responses:

https://marketplace.firefox.com/api/v\d+/fireplace/search/featured/.*
https://marketplace.firefox.com/api/v\d+/apps/category/.*
https://marketplace.firefox.com/api/v\d+/apps/search/.*

These are API responses that contain no user information and are loaded from the homepage, category landing, and search results pages, respectively.

Bug 957387 was to investigate whether we can do this. And we can, even with async cache refreshing, but this is blocked on Akamai at the moment.

When Akamai gets the ball rolling, we can get the ball rolling on this. I'm excited!
Depends on: 989056
https://github.com/mozilla/fireplace/commit/076871a

Jeremy set up on Cloudflare on -dev, and I hooked up our search, category, and featured (homepage) API responses to it :)

On fast wifi:
http://f.cl.ly/items/0I1G2B1X112i2D2P2L0T/Screen%20Shot%202014-03-27%20at%205.37.56%20PM.png

WOOHOOOOO!!!

Sub-EDGE (48K):
http://f.cl.ly/items/043P2F3J2c0H2Z1r3I2X/Screen%20Shot%202014-03-27%20at%205.41.39%20PM.png
Assignee: nobody → cvan
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-04-01
When loading https://marketplace-dev.allizom.org/ I see it's requesting https://marketplace-dev.mozflare.net/ for assets but it's using https://marketplace-dev-cdn.allizom.org/ for the search/featured XHR request:

https://marketplace-dev-cdn.allizom.org/api/v1/fireplace/search/featured/?cache=1&cat=&lang=en-US&region=restofworld&vary=0

In console:

>>> require('settings').cdn_url
"https://marketplace-dev-cdn.allizom.org"

>>>require('settings').media_url
" https://marketplace-dev-cdn.allizom.org/media"

(Note the space in media_url, and the fact that it's not using mozflare in both)


I saw this in both Firefox and Chrome.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed, thanks: https://github.com/mozilla/fireplace/commit/9af76d3
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Please add STR here or mark it with [qa-] if no QA is needed.
Flags: needinfo?(cvan)
Flags: needinfo?(cvan)
Whiteboard: [qa-]
Flags: needinfo?(cvan)
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.