You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 11, 2021. It is now read-only.
The time difference between a Model.objects.all() and cache.get on our database isn't particularly large, for example with gargoyle data:
In [13]: %timeit list(Switch.objects.all())
100 loops, best of 3: 2.71 ms per loop
In [14]: %timeit caches['gargoyle'].get('SwitchManager:Switch:key')
1000 loops, best of 3: 1.18 ms per loop
Why don't we just stop using Django's cache system? It's making misses a lot more complicated...
The text was updated successfully, but these errors were encountered:
The time difference between a
Model.objects.all()
andcache.get
on our database isn't particularly large, for example with gargoyle data:Why don't we just stop using Django's cache system? It's making misses a lot more complicated...
The text was updated successfully, but these errors were encountered: