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 2020/04/02 14:47:00 UTC

[jira] [Updated] (IGNITE-12691) .NET: Native Near Cache

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

Pavel Tupitsyn updated IGNITE-12691:
------------------------------------
    Release Note: Add .NET native Near Cache

> .NET: Native Near Cache
> -----------------------
>
>                 Key: IGNITE-12691
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12691
>             Project: Ignite
>          Issue Type: New Feature
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>              Labels: .NET
>             Fix For: 2.9
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Implement native .NET Near Cache, which stores deserialized cache data on CLR heap.
> Right now every cache.Get, every scan query, etc, cause repeated copy and deserialization of data from JVM, even for primary keys or near cache entries. This often becomes a bottleneck. Keeping up-to-date deserialized values in CLR memory can greatly improve performance and reduce latency.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)