You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2018/06/21 13:42:00 UTC

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

Alexei Scherbakov created IGNITE-8846:
-----------------------------------------

             Summary: Optimize entry transform operations.
                 Key: IGNITE-8846
                 URL: https://issues.apache.org/jira/browse/IGNITE-8846
             Project: Ignite
          Issue Type: Improvement
            Reporter: Alexei Scherbakov
            Assignee: Alexei Scherbakov


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)