You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:00:01 UTC
[jira] [Updated] (IGNITE-9688) MVCC: Implement out-of-order enlist
optimization for bulk cache operations.
[ https://issues.apache.org/jira/browse/IGNITE-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-9688:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> MVCC: Implement out-of-order enlist optimization for bulk cache operations.
> ---------------------------------------------------------------------------
>
> Key: IGNITE-9688
> URL: https://issues.apache.org/jira/browse/IGNITE-9688
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: mvcc_performance, performance
> Fix For: 2.9
>
>
> For now, we always enlist updates in given order via setting "GridNearTxEnlistFuture.sequential" flag to true.
> This flag is always true for query updates as we do not know full data set at a time future has been created.
> For putAll (and other batch operations) full update map is known and we can make per-node batches full filled before send.
> E.g. we can send batches to nodes one by one regarding primary node order.
> This optimization has to be disscussed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)