Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
The current use of the protobuf API uses an expensive code path. The builder uses the parser to instantiate a message, then copies the message into the builder. The parser is creating multi-layered internally buffering streams that cause excessive byte[] allocations.
Using the parser directly with a coded input stream backed by the byte[] from the wire will take a fast-path straight to the pb message's ctor. Substantially less garbage is generated.
Attachments
Attachments
Issue Links
- breaks
-
HADOOP-13473 Tracing in IPC Server is broken
- Resolved
- is required by
-
HADOOP-13465 Design Server.Call to be extensible for unified call queue
- Resolved
- requires
-
HADOOP-13426 More efficiently build IPC responses
- Resolved