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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/12/22 13:01:01 UTC

[jira] [Updated] (IGNITE-1914) .Net: Get rid of boxing in DoOutInOpNullable

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

Vladimir Ozerov updated IGNITE-1914:
------------------------------------
    Labels: .net performance  (was: .net)

> .Net: Get rid of boxing in DoOutInOpNullable
> --------------------------------------------
>
>                 Key: IGNITE-1914
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1914
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>            Priority: Minor
>              Labels: .net, performance
>             Fix For: 2.0
>
>
> See CacheImpl.DoOutInOpNullable overloads.
> We read result as object and then check for null. Nulls are quite frequent in these scenarios.
> To get rid of boxing we need to introduce TryUnmarshal method which allows reading value types with null semantics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)