You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (JIRA)" <ji...@apache.org> on 2018/09/24 18:30:00 UTC

[jira] [Updated] (IGNITE-7115) .NET: Thin client: performance: use buffer pool

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

Nikolay Izhikov updated IGNITE-7115:
------------------------------------
    Fix Version/s:     (was: 2.7)
                   2.8

> .NET: Thin client: performance: use buffer pool
> -----------------------------------------------
>
>                 Key: IGNITE-7115
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7115
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>    Affects Versions: 2.4
>            Reporter: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, performance
>             Fix For: 2.8
>
>
> Currently we allocate a lot of {{byte[]}} arrays for socket operations, which is suboptimal, especially for large arrays which go to Large Object Heap.
> Use a shared buffer pool instead, see {{PlatformMemoryPool}} for reference.
> Make sure to maintain correct detachment semantics: {{BinaryReader.ReadAsBinary}} in some cases may pass streamed array to user code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)