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

Provide an explicit Cache API #887

Open
Morendil opened this issue Jun 7, 2019 · 1 comment · May be fixed by #1167
Open

Provide an explicit Cache API #887

Morendil opened this issue Jun 7, 2019 · 1 comment · May be fixed by #1167
Labels
kind:discovery Issue requires discovery: value, ux and tech

Comments

@Morendil
Copy link
Contributor

Morendil commented Jun 7, 2019

Following discussions on #871 (on here and IRL with @fpagnoux) we've identified a few "sticks" that should be moved out of the way before implementing some performance optimizations that seem quite promising (split-and-combine, and possibly later taking advantage of static analysis to prune the computation tree ahead of time).

These include #885 and #886 to warm up. The next significant bit is to make the caching API explicit.

@bonjourmauko
Copy link
Member

A tl;dr of previous efforts was to:

  1. Move the cache from the variables to the simulation.
  2. Have a way of rewinding or itemising calculations.
  3. Separate cache and storage layers.

@bonjourmauko bonjourmauko linked a pull request Oct 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:discovery Issue requires discovery: value, ux and tech
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants