[
https://issues.apache.org/jira/browse/IGNITE-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1811:
--------------------------------
Description:
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.
was:
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
> 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: Improvement
> Reporter: Yakov Zhdanov
> Assignee: Yakov Zhdanov
> Priority: Blocker
> Fix For: 1.6
>
> Attachments: Screenshot 2015-10-29 18.04.07.png
>
>
> 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)
