You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 08:19:00 UTC

[jira] [Assigned] (IGNITE-10730) MVCC TX: Batch WAL datarecords

     [ https://issues.apache.org/jira/browse/IGNITE-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov reassigned IGNITE-10730:
----------------------------------------

    Assignee:     (was: Andrew Mashenkov)

> MVCC TX: Batch WAL datarecords
> ------------------------------
>
>                 Key: IGNITE-10730
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10730
>             Project: Ignite
>          Issue Type: Task
>          Components: mvcc
>            Reporter: Igor Seliverstov
>            Priority: Major
>              Labels: mvcc_performance
>
> 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)