Skip to content
This repository has been archived by the owner on Nov 14, 2022. It is now read-only.

Investigate Django caching #193

Open
Pasarus opened this issue Aug 18, 2022 · 0 comments
Open

Investigate Django caching #193

Pasarus opened this issue Aug 18, 2022 · 0 comments

Comments

@Pasarus
Copy link
Member

Pasarus commented Aug 18, 2022

Issue raised by: [developer]

What?
Django has many built-in caching solutions that we are not making use of. See here.
There are many areas I believe we could implement caching.

Some examples I have thought of:

  • Cache the overview page. Small performance gain, as we will no longer to query for the instruments every time. This cache could have a long expiration time. Template fragment caching could work

  • Caching run summaries. It should be possible to cache the run summary page (or a fragment of the template) for each version of a run. This could (potentially) allow the plot to be cached at the same time, allowing a lot of logic to be removed plot_handler

Care must be taken to make sure any logic is not called if a cache is available. It is possible to implement a cache, execute queries, then ignore the result and use the cache. We must avoid that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant