You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Dudkov (JIRA)" <ji...@apache.org> on 2017/04/06 10:58:42 UTC
[jira] [Updated] (IGNITE-4571) Optimize futVer generations
[ https://issues.apache.org/jira/browse/IGNITE-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Dudkov updated IGNITE-4571:
--------------------------------------
Fix Version/s: 2.0
> 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
> Fix For: 2.0
>
>
> 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.15#6346)