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

Reuse serialized data in Router #69

Closed
jimfcarroll opened this issue Oct 6, 2012 · 1 comment
Closed

Reuse serialized data in Router #69

jimfcarroll opened this issue Oct 6, 2012 · 1 comment
Assignees
Milestone

Comments

@jimfcarroll
Copy link
Collaborator

With dynamic topology the likelihood of forks in the processing pipeline increases, but the fact is an entire topology PROBABLY uses the same serializer. In this case it makes sense to reuse the serialized data in the transport.send method rather than reserialize the object to be sent.

@ghost ghost assigned jimfcarroll Oct 6, 2012
@jimfcarroll jimfcarroll added this to the 0.9 milestone May 8, 2017
@jimfcarroll
Copy link
Collaborator Author

The 0.9 codebase currently in master allows has made serialization an implementation detail of the transport. The NioTransport is "zero copy" but if the message is sent to multiple nodes it will be reserialized in each one. This wont be addressed any time soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant