[
https://issues.apache.org/jira/browse/IGNITE-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-17821:
------------------------------------
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.
> Thin 3.0 Perf: Implement BinaryTupleReader and Builder over ByteBuf
> -------------------------------------------------------------------
>
> Key: IGNITE-17821
> URL: https://issues.apache.org/jira/browse/IGNITE-17821
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
