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

add 'variables' parameters for view.update() #13

Open
robin-cls opened this issue Oct 25, 2024 · 1 comment · May be fixed by #14
Open

add 'variables' parameters for view.update() #13

robin-cls opened this issue Oct 25, 2024 · 1 comment · May be fixed by #14
Assignees

Comments

@robin-cls
Copy link

A Collection can specify the variables that will be updated using the Collection.update() method. This prevents zcollection having to guess the updated variables by launching the callback over the first partition. This is very useful if the callback needs heavy auxiliary data that can only be loaded on a dask worker.

A View cannot use the same 'variables' and cannot bypass this variables inference step. It would be a great for View.update() to have the same behavior as the Collection

@robin-cls
Copy link
Author

In addition, the current view.update() needs to have the updated variables in the selected variables. This can cause a significant supplementary memory usage in case we work with delayed=False.
Hopefully, adding the 'variables' parameter will remove the need to put the updated variables in the 'selected_variables' parameters

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 a pull request may close this issue.

2 participants