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/02 09:50:00 UTC

[jira] [Updated] (IGNITE-19632) .NET: Thin 3.0: Optimize Data Streamer for single connection use case

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

Pavel Tupitsyn updated IGNITE-19632:
------------------------------------
    Description: 
Optimize .NET client data streamer for a use case when only one connection exists. In this case we don't need to deal with partition awareness and per-node buffers.

This can be detected automatically or by a flag in DataStreamerOptions.

  was:
Optimize Java client data streamer for a use case when only one connection exists. In this case we don't need to deal with partition awareness and per-node buffers.

This can be detected automatically or by a flag in DataStreamerOptions.


> .NET: Thin 3.0: Optimize Data Streamer for single connection use case
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-19632
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19632
>             Project: Ignite
>          Issue Type: Task
>          Components: thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: iep-102, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Optimize .NET client data streamer for a use case when only one connection exists. In this case we don't need to deal with partition awareness and per-node buffers.
> This can be detected automatically or by a flag in DataStreamerOptions.



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