[
https://issues.apache.org/jira/browse/IGNITE-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073780#comment-17073780
]
Ignite TC Bot commented on IGNITE-12691:
----------------------------------------
{panel:title=Branch: [pull/7605/head] Base: [master] : Possible Blockers
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5182649]]
{color:#d04437}MVCC Cache 7{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5182675]]
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5182639]]
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5182635]]
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5182661]]
* IgniteBinaryCacheQueryTestSuite: SqlViewExporterSpiTest.testSchemas - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5182685&buildTypeId=IgniteTests24Java8_RunAll]
> .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: 0.5h
> 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)
