[jira] [Commented] (IGNITE-8846) Optimize entry transform operations.

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-8846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948432#comment-16948432 ] 

Maxim Muzafarov commented on IGNITE-8846:
-----------------------------------------

Moved to 2.9 due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.


> 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.8
>
>
> 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
(v8.3.4#803005)