You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/31 13:36:25 UTC

[jira] [Updated] (IGNITE-1811) Get from backup in Dht cache can be optimized

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

Vladimir Ozerov updated IGNITE-1811:
------------------------------------
    Issue Type: Task  (was: Sub-task)
        Parent:     (was: IGNITE-2232)

> Get from backup in Dht cache can be optimized
> ---------------------------------------------
>
>                 Key: IGNITE-1811
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1811
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Yakov Zhdanov
>            Assignee: Semen Boikov
>            Priority: Blocker
>              Labels: 1.5.4, performance
>             Fix For: 1.6
>
>         Attachments: Main.java, Screenshot 2015-10-29 18.04.07.png, test.csv
>
>
> Reproducible example: https://gist.github.com/aboudnik/3419fdc3872cc3051a1d
> See attached screenshot for sampling info.
> Issues found:
> # entry is created with putIfObsoleteOrAbsent() even if store and swap are disabled
> # no need to create DhtGetFuture on primary when there is no ongoing rebalancing 
> Make sure the performance is fixed for ATOMIC and TRANSACTIONAL REPLICATED & PARTITIONED caches.



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