Closed Bug 1242982 Opened 8 years ago Closed 7 years ago

Use instance cache for v2 relationship links

Categories

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Whiteboard: [bc:infra][bc:milestone=spaceship])

What did you do?
================
1. Turn on DEBUG and the Django Debug Toolbar, enable cache backend
2. Go to /api/v2/browsers/1/relationships/versions
3. Refresh /api/v2/browsers/1/relationships/versions


What happened?
==============
8 SQL queries and no Cache calls are used to render the response

What should have happened?
==========================
With a warmed cache, 1 SQL query is expected at most, to load the auth user. 1 Cache call should be used to render the response

Is there anything else we should know?
======================================
When a relationships link is followed, a CachedModel should be used for the primary instance.
Blocks: 996570
Mentor: jwhitlock
Whiteboard: [specification][type:bug] → [bc:infra][bc:milestone=spaceship]
Mentor: jwhitlock
The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.