ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yakov Zhdanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4571) Optimize futVer generations
Date Fri, 20 Jan 2017 11:37:26 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831581#comment-15831581
] 

Yakov Zhdanov commented on IGNITE-4571:
---------------------------------------

[~kdudkov]
Agree with [~vozerov].

Please consider the recommendation. 

> Optimize futVer generations
> ---------------------------
>
>                 Key: IGNITE-4571
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4571
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Konstantin Dudkov
>            Assignee: Konstantin Dudkov
>
> 1. Optimize futVer generations - need to get rid of using CacheVersion in favor of long
value.
> Example
> org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateFuture.java:633
> org.apache.ignite.internal.processors.cache.version.GridCacheVersionManager#next(org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion)
> Result:
> Need to replace cache version with random long (int), check compatibility and messages
sizes before & after and benchmark.
> How:
> Use thread local random. Generate ID on atomic future store and switch it to putIfAbsent().



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

Mime
View raw message