[ https://issues.apache.org/jira/browse/IGNITE-8846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623557#comment-16623557 ]
Nikolay Izhikov commented on IGNITE-8846: ----------------------------------------- [~ascherbakov] Do we have a chance to resolve this ticket until the code freeze of 2.7? > Optimize entry transform operations. > ------------------------------------ > > Key: IGNITE-8846 > URL: https://issues.apache.org/jira/browse/IGNITE-8846 > Project: Ignite > Issue Type: Improvement > Affects Versions: 2.5 > Reporter: Alexei Scherbakov > Assignee: Alexei Scherbakov > Priority: Major > Fix For: 2.7 > > > 1. For pessimistic transactions entryProcessor is invoked twice if tx entry > is already exists in [1] > and after lock acquistion in [2] > Actually this is enough to do it only once in postLockWrite. > 2. Cache entry value is not needed on near node if EntryProcessor declares > Void return type. > We should try to detect this in runtime or provide some kind of annotation to > mark EntryProcessor not caring about return value. This will bring huge > performance benefit for transactions updating large values using > transformations. > [1] > org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#enlistWriteEntry > [2] > org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter#postLockWrite -- This message was sent by Atlassian JIRA (v7.6.3#76005)