Closed Bug 905967 Opened 12 years ago Closed 12 years ago

Add django-cache-machine to UserProfile model

Categories

(Mozilla Reps Graveyard :: reps.mozilla.org, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nemo-yiannis, Assigned: nemo-yiannis)

References

Details

(Whiteboard: [kb=1080148] [qa-])

Some of ReMo DB models heavily favor reads over writes. We can make some optimization improvements by adding django-cache-machine to that models. The first 2 that we can start are: * FunctionalArea (rarely change) * UserProfile
Assignee: nobody → jgiannelos
Group: mozilla-reps-admins
Whiteboard: [kb=1080148]
Due to that [1] issue we can't enable cache-machine to FunctionalArea. [1] https://github.com/jbalogh/django-cache-machine/issues/23
Summary: Add django-cache-machine to remo backend → Add django-cache-machine to UserProfile model
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Did some verification on Edit Profile, reviewed the changes made on github. Please add specific steps if anything else is needed.
I don't think there is a way to verify django-cache-machine to the portal page. I assume that this is QA-.
Verified as [qa-]
Status: RESOLVED → VERIFIED
Whiteboard: [kb=1080148] → [kb=1080148] [qa-]
OS: Linux → All
Hardware: x86_64 → All
Version: unspecified → 411
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in before you can comment on or make changes to this bug.