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/01/11 16:15:40 UTC

[jira] [Updated] (IGNITE-1969) .NET: Optimize PlatformCache "loadCache" and "readScanQuery" methods.

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

Vladimir Ozerov updated IGNITE-1969:
------------------------------------
    Fix Version/s:     (was: 1.6)

> .NET: Optimize PlatformCache "loadCache" and "readScanQuery" methods.
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-1969
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1969
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>
> Earlier we have an optimization when we passed pointer to .Net object along with its serialized form to avoid deserialization for node-local scenarios. But then we revealed leaks in implementation and disabled this opto.
> As as result we always pass 0 to corresponding native methods (see loadCache0 and readScanQuery). 
> We need either re-apply this opto correctly, or refactor native methods and forget about.



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