You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Yuxuan Wang (Jira)" <ji...@apache.org> on 2020/09/22 21:45:00 UTC

[jira] [Created] (THRIFT-5279) Cleanups/small optimizations for go's serializer/deserializer code

Yuxuan Wang created THRIFT-5279:
-----------------------------------

             Summary: Cleanups/small optimizations for go's serializer/deserializer code
                 Key: THRIFT-5279
                 URL: https://issues.apache.org/jira/browse/THRIFT-5279
             Project: Thrift
          Issue Type: Task
          Components: Go - Library
    Affects Versions: 0.13.0
            Reporter: Yuxuan Wang
            Assignee: Yuxuan Wang


Currently go's default NewTSerializer and NewTDeserializer implementations use NewTBinaryProtocolFactoryDefault().GetProtocol(transport) to get the protocol. This is essentially the same as NewTBinaryProtocolTransport(transport), but with an extra allocation of the ProtocolFactory that is only used once then discarded. Streamline it will give as a minor performance gain.

Also I plan to add new constructors for TSerializerPool and TDeserializerPool to make it easier to use with non-default protocols.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)