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

Optimization with user interest & conversion caching #154

Open
softmarshmallow opened this issue Aug 28, 2021 · 0 comments
Open

Optimization with user interest & conversion caching #154

softmarshmallow opened this issue Aug 28, 2021 · 0 comments

Comments

@softmarshmallow
Copy link
Member

softmarshmallow commented Aug 28, 2021

Selection conversion to Reflect UI Node is required by user interest, and is not required when, for example, Icons loader is selected.

Also with node caching we can save converting resource, still few problem remains.

  • Timestamp management for converted data cache
  • Tree inspection logic to check if the node is actually changed and requires re-conversion
  • Only convert the updated node (if possible)
  • Q: Can we make tree inspection to check anything is updated as a cheap operation? (or will it be cheaper to just convert the whole tree? )
  • Size management to ask user to update it again (e.g. "Your have selected a huge layer. Do you want to proceed?" + "You have selected a huge layer. Do you want to use cached version of it to save time?")

Related - https://github.com/gridaco/assistant/tree/optimize/with-user-interest

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