[IGNITE-17821] Thin 3.0 Perf: Implement BinaryTupleReader and Builder over ByteBuf

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.1
• Component/s: thin client
• Labels: iep-92 ignite-3
• Epic Link: AI3 Performance
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 04/Oct/22 12:26
• Updated: 04/Sep/24 16:29

Description

Client protocol uses BinaryTuple for data transfer (rows, compute args, etc). In many cases we need to read or write BinaryTuple from/to ByteBuf. Currently this requires conversion between Netty ByteBuf to NIO ByteBuffer, sometimes involving buffer copy operations (see ClientMessageUnpacker.readBinaryUnsafe, ClientMessagePacker.packBinaryTuple and their usages).

Implement BinaryTuple reader and writer that work directly with Netty ByteBuf.

Issue Links

• is blocked by: IGNITE-17636 Thin 3.0: Avoid BinaryTuple conversion in client handler
• is blocked by: IGNITE-18925 Thin 3.0: Avoid BinaryTuple conversion from client to storage