You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case(s) - what problem will this feature solve?
We have server that sends really large payloads, our benchmarks shows that most of the cpu time on server is used for serialization. we tried caching the PreparedMsgs and sending them and we saw a huge improvement.
Use case(s) - what problem will this feature solve?
We have server that sends really large payloads, our benchmarks shows that most of the cpu time on server is used for serialization. we tried caching the
PreparedMsg
s and sending them and we saw a huge improvement.Proposed Solution
#3480
Alternatives Considered
We are now using a custom Codec and send
[]byte
instream.SendMsg()
as a workaround.Additional Context
#2432
The text was updated successfully, but these errors were encountered: