You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2025/01/20 17:22:00 UTC

[jira] [Resolved] (IGNITE-24107) Allow to use an existing buffer in BinaryTupleBuilder

     [ https://issues.apache.org/jira/browse/IGNITE-24107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Pereslegin resolved IGNITE-24107.
---------------------------------------
    Resolution: Won't Fix

Our use cases tests did not reveal 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: 10m
>  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)