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

Model Caching #38

Open
ztnel opened this issue Jun 19, 2022 · 0 comments
Open

Model Caching #38

ztnel opened this issue Jun 19, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ztnel
Copy link
Owner

ztnel commented Jun 19, 2022

I think it makes more sense to enforce all state models to cache all the time. The reason is because all definitions that are state models and have those caching functions defined should use them always instead of requiring developers to include cache=True for each state commit they want to cache. That requires remembering to cache that specific model type every instance its changed. Instead the decision whether model changes should be cached should be decided when that model is defined so the system caches it all the time. The disadvantage of making caching granular at the model level means that fast updating parts of a model constrain the ability for that whole model to be cached efficiently since it involves disk writes.

@ztnel ztnel added the enhancement New feature or request label Jun 19, 2022
@ztnel ztnel self-assigned this Jun 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant