You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Stronchinskiy (Jira)" <ji...@apache.org> on 2023/04/10 14:15:00 UTC

[jira] [Assigned] (IGNITE-17244) .NET: Thin 3.0: Optimize async request handling

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

Sergey Stronchinskiy reassigned IGNITE-17244:
---------------------------------------------

    Assignee: Sergey Stronchinskiy  (was: Pavel Tupitsyn)

> .NET: Thin 3.0: Optimize async request handling
> -----------------------------------------------
>
>                 Key: IGNITE-17244
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17244
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Sergey Stronchinskiy
>            Priority: Minor
>              Labels: .NET, ignite-3
>
> Reduce allocations when handling async requests in *ClientSocket*.
> Look into combining the following functionality into a single object that can be pooled:
> * IBufferWriter - to write the request
> * IValueTaskSource - to represent the task completion
> * IThreadPoolWorkItem - to handle response on thread pool efficiently
> See PoolingAsyncValueTaskMethodBuilder details: https://devblogs.microsoft.com/dotnet/how-async-await-really-works/



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