ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-8846) Optimize entry transform operations.
Date Thu, 21 Jun 2018 13:42:00 GMT
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

View raw message