Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on best cache timeout and improve caching of absolute and relative datetime data #28

Open
cortadocodes opened this issue Mar 21, 2023 · 0 comments

Comments

@cortadocodes
Copy link
Member

The cache is currently set to an hour, meaning if trying to display data for the same set of inputs on the dashboard within an hour, the database is not re-queried and the same results are shown. The timeout could be increased (for fewer database queries) or decreased (for quicker access to the latest data).

Caching could also be set up in a more adaptable way so that absolute datetime data is cached for much longer while relative datetime data is cached for less time.

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

No branches or pull requests

1 participant