[
https://issues.apache.org/jira/browse/IGNITE-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728275#comment-16728275
]
Ignite TC Bot commented on IGNITE-10730:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 5.3{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2614050]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2614051&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
