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 Tupitsyn (Jira)" <ji...@apache.org> on 2023/06/29 07:05:00 UTC

[jira] [Updated] (IGNITE-19879) .NET: Avoid allocating separate buffer for BinaryTupleBuilder

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

Pavel Tupitsyn updated IGNITE-19879:
------------------------------------
    Ignite Flags:   (was: Docs Required,Release Notes Required)

> .NET: Avoid allocating separate buffer for BinaryTupleBuilder
> -------------------------------------------------------------
>
>                 Key: IGNITE-19879
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19879
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> In most cases we already have a *PooledArrayBuffer* at hand when we create a *BinaryTupleBuilder*. There is no reason to allocate another buffer, we should be able to write directly to the existing one.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)