[
https://issues.apache.org/jira/browse/IGNITE-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042683#comment-17042683
]
Pavel Tupitsyn commented on IGNITE-12691:
-----------------------------------------
[~GuruStron] [~isapego] PR is ready for preliminary review:
* Feature core is ready and covered with tests (configuration, updates,
expiration, invalidation)
* Put/Get and a few more cache operations are ready. Others are in progress.
* Please ignore missing xmldoc and other minor things for now
> .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: 10m
> 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)
