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

Have IO serialization be opt-in/-out #156

Open
liamhuber opened this issue Jan 16, 2023 · 0 comments
Open

Have IO serialization be opt-in/-out #156

liamhuber opened this issue Jan 16, 2023 · 0 comments
Assignees
Labels
feature request request partner of "enhancement"

Comments

@liamhuber
Copy link
Member

Joerg requested that we give node designers explicit access to a flag specifying the priority to serialize port values on session serialization. By default I imagine all input values should have a high serialization priority, while all output values should by default have a low serialization priority. Values could be on a scalar field, and the user could then specify a priority threshold for serialization.

I can imagine also exposing this priority in the node controller, so it can be tweaked for particular graphs if you really want to optimize storage -- e.g. even DataNodes don't need to bother serializing their input if it's already connected.

For that matter, maybe we can automate it so that being connected automatically drops the serialization priority for input...

@liamhuber liamhuber added the feature request request partner of "enhancement" label Jan 16, 2023
@liamhuber liamhuber self-assigned this Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request request partner of "enhancement"
Projects
None yet
Development

No branches or pull requests

1 participant