[
https://issues.apache.org/jira/browse/IGNITE-24107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914740#comment-17914740
]
Pavel Pereslegin edited comment on IGNITE-24107 at 1/20/25 5:23 PM:
--------------------------------------------------------------------
Our use case benchmarks did not show any noticeable improvements in memory
allocation/performance, so we decided to leave BinaryTupleBuilder with internal
byte buffer allocation for now.
was (Author: xtern):
Our use case benchs did not show any noticeable improvements in memory
allocation/performance, so we decided to leave BinaryTupleBuilder with internal
byte buffer allocation for now.
> Allow to use an existing buffer in BinaryTupleBuilder
> -----------------------------------------------------
>
> Key: IGNITE-24107
> URL: https://issues.apache.org/jira/browse/IGNITE-24107
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maksim Zhuravkov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Sometimes we want to write a tuple into an existing buffer but
> BinaryTupleBuilder always allocates a new buffer for each binary tuple it
> builds. Let's update BinaryTupleBuilder to accept a component that allocates
> a buffer used by BinaryTupleBuilder.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
