Redesign serialization #425
cBournhonesque
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current serialization/replication is not performant because:
we have extra allocations when building intermediate data structures
we might be sending too many small messages which creates a lot of extra bandwidth?
Maybe get rid of ReplicationGroup altogether? or instead of just creating a small message for the replication group, we create one big message by default. Except if a replication group is specified.
Beta Was this translation helpful? Give feedback.
All reactions