investigate caching for assets/ call

[hburgund]

The assets/ endpoint works fine for small number of assets, but when there are thousands of assets, it starts to take a long time to return the result which in turn causes major slow-downs on the client-side.

Ideally, all calls to assets/ would have an optional parameter to take the cached response or not and the cached response would automatically be updated server-side every time a new asset is added.

It is crucial that clients are able to grab the most recent data because when a client adds a new asset, they will want it to show up on the map, for example, right away.

It is likely that the assets/ code can be optimized to improve efficiency, but this may not be enough to really fix the current problem, hence the caching research.

Resources

• http://chibisov.github.io/drf-extensions/docs/#cache-response
• https://github.com/Onyo/django-rest-framework-cache

[hburgund]

significant optimization work done using prefetch_related and select_related that speeds up call in some cases by order of magnitude: 1ecb0f2

caching is likely still a good idea, but this is a major improvement.