[
https://issues.apache.org/jira/browse/IGNITE-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726067#comment-16726067
]
ASF GitHub Bot commented on IGNITE-10730:
-----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5714
IGNITE-10730: Batch mvcc wal records in tx.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10730
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5714.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5714
----
commit dfe77f6d85c28ad8ef97447105a1480ce43bee8a
Author: Andrey V. Mashenkov <andrey.mashenkov@...>
Date: 2018-12-20T17:32:19Z
IGNITE-10730: WIP.
----
> MVCC TX: Batch WAL datarecords
> ------------------------------
>
> Key: IGNITE-10730
> URL: https://issues.apache.org/jira/browse/IGNITE-10730
> Project: Ignite
> Issue Type: Improvement
> Components: mvcc
> Reporter: Igor Seliverstov
> Assignee: Andrew Mashenkov
> Priority: Major
>
> on MVCC updates we make changes one by one and WAL records are written
> straight after successful update under the same checkpoint lock. This
> produces contention on wal flush operations and harm overall performance. But
> we need only one guarantee - all the records have to be written into the log
> before prepare start. That means we free to batch such writes (for example 10
> rows in one data record) it shouldn't cause memory issues but will resolve
> contention.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
