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

precision topology_view caching #111

Open
eagmon opened this issue Dec 1, 2021 · 0 comments
Open

precision topology_view caching #111

eagmon opened this issue Dec 1, 2021 · 0 comments

Comments

@eagmon
Copy link
Member

eagmon commented Dec 1, 2021

If a '_generate' or '_divide' update is triggered it requires the expiration and re-caching of some topology_views. Currently, Store.apply_update will pass a view_expire flag (here) back to Engine, which triggers self.state.build_topology_views(): (here). This expires and re-caches ALL of the topology_views across the entire Store hierarchy. It would be more efficient if it knew to only expire and re-cache the topology_view of the subset of processes that are connected to the affected stores.

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