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 2017/09/20 10:08:02 UTC
[jira] [Assigned] (IGNITE-6309) .NET: Thin client: Do not buffer
entire socket response
[ https://issues.apache.org/jira/browse/IGNITE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn reassigned IGNITE-6309:
--------------------------------------
Assignee: (was: Pavel Tupitsyn)
> .NET: Thin client: Do not buffer entire socket response
> -------------------------------------------------------
>
> Key: IGNITE-6309
> URL: https://issues.apache.org/jira/browse/IGNITE-6309
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Priority: Minor
> Labels: .NET, performance
> Fix For: 2.3
>
>
> See {{ClientSocket.SendReceive}}: it buffers entire socket response into an array. Responses can be huge (with {{QueryCursor.GetAll}} and the like), so this can cause LOH allocations.
> We should implement {{IBinaryStream}} over a socket instead.
> This may cause situation when another socket call happens in the middle of data transfer (for example, GetBinaryTypeName while reading cursor data).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)