[
https://issues.apache.org/jira/browse/IGNITE-29249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18137954#comment-18137954
]
Ignite TC Bot commented on IGNITE-29249:
----------------------------------------
{panel:title=Branch: [pull/13788/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13788/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9470205&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9470205
rerunBuildIds=9470207,9470209{color}
> Reduce allocations on the cache get path
> ----------------------------------------
>
> Key: IGNITE-29249
> URL: https://issues.apache.org/jira/browse/IGNITE-29249
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Major
> Fix For: 2.20
>
> Attachments: JmhCacheRemoteGetBenchmark.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Two sources of pure overhead on the hottest cache path:
> *DHT side of a remote get.* {{GridDhtGetFuture}} and
> {{GridDhtGetSingleFuture}} allocate a future ID and a new cache version that
> nobody reads. The version counter is bumped under contention for every read.
> *Cluster state check on every cache operation.* Each operation on a cache
> proxy calls {{{}publicApiState{}}}, which builds a finished future and a
> chain even when no state transition is in progress, i.e. in the normal steady
> state of the cluster.
> Both can be removed without changing the behaviour.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
