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

Refactor in-memory caching #6056

Merged
merged 5 commits into from
Sep 22, 2020
Merged

Refactor in-memory caching #6056

merged 5 commits into from
Sep 22, 2020

Conversation

sulkaharo
Copy link
Member

  • Now supports cache updates and flushing from persistence layer, so treatment updates and removes are immediately reflected in runtime state
  • Cleaner separation of concerns between data loader and caching

* Refactoring the cache: moved to another file and support flushing from bus events
…use the new model and reduce queries back down
@bewest
Copy link
Member

bewest commented Sep 20, 2020

This looks like it extends the previous effort all the way to the storage layer for each collection.

Do we have any idea which apps or how many people would be affected by an app with degraded performance due to rejected entries? Arguably "none" since that data is essentially orphaned.

* Remove the validation for created_at in REST API ;(
@sulkaharo sulkaharo merged commit cde9aa3 into dev Sep 22, 2020
@sulkaharo
Copy link
Member Author

Merged given thumbs up from multiple testers, including AAPS users

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

Successfully merging this pull request may close these issues.

2 participants