Closed Bug 1093222 Opened 10 years ago Closed 9 years ago

ditch django-cache-machine

Categories

(Input Graveyard :: Backend, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2015q1

People

(Reporter: willkg, Assigned: rrosario)

References

Details

(Whiteboard: u=dev c=codequality p=1 s=input.2015q1)

django-cache-machine is poorly maintained in the sense that they never put out releases and doing the sorts of things maintainers should be doing for a properly maintained project.

Ricky pointed out that Input probably doesn't need django-cache-machine at all. Most of the "fetch" kinds of things pull from ES and not the db. We could easily write a mini-caching layer for the few things that pull from the db that actually need to be cached.

This bug covers researching removing django-cache-machine and examining whether it will create performance issues if we do.
Jannis said they ditched it on MDN and haven't been happier.

I think that suggests we should just ditch it and then fix performance issues as they come up.
Whiteboard: u=dev c=codequality p= s=input.2015q1
Whiteboard: u=dev c=codequality p= s=input.2015q1 → u=dev c=codequality p= s=input.adam
Tossing this in the 2015q1 queue.
Whiteboard: u=dev c=codequality p= s=input.adam → u=dev c=codequality p= s=input.2015q1
Might as well ditch this before the Django upgrade to simplify things.
Blocks: 1118765
Gonna work on this todayish.
Assignee: nobody → rrosario
Target Milestone: --- → 2015q1
I think this was about 1pt.
Whiteboard: u=dev c=codequality p= s=input.2015q1 → u=dev c=codequality p=1 s=input.2015q1
willkg just deployed to prod.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.